DanConwayDev on Nostr: I have fixed this on the master branch. I'll push a v1.4.6 shortly to patch v1.4. ...
I have fixed this on the master branch. I'll push a v1.4.6 shortly to patch v1.4.
with the fix your branch could be called `article-editor` or `pr/article-editor`
if you are logged in as the author of the PR (git config nostr.npub matches the PR author)
or `article-editor(3fbba0ec)` which is what it would be named if you weren't logged in as the author and checked out the branch on a remote with the nostr url.
I think there might be other problems with the repo (potentially stemming from oversized patches). Hence the need for blossom for large patches and the discussion we were going to have.
with the fix your branch could be called `article-editor` or `pr/article-editor`
if you are logged in as the author of the PR (git config nostr.npub matches the PR author)
or `article-editor(3fbba0ec)` which is what it would be named if you weren't logged in as the author and checked out the branch on a remote with the nostr url.
I think there might be other problems with the repo (potentially stemming from oversized patches). Hence the need for blossom for large patches and the discussion we were going to have.