@DanConwayDev on ngit 1.4.5, when I try to run `ngit push` or `ngit pull`, I get the following message: > Error: cannot find proposal that matches the current branch name The branch name on my local computer is `article-editor`, and I'm trying to push updates to the below proposal on GitWorkshop: nostr:nevent1qvzqqqqx2ypzquqjyy5zww7uq7hehemjt7juf0q0c9rgv6lv8r2yxcxuf0rvcx9eqydhwumn8ghj7argv43kjarpv3jkctnwdaehgu339e3k7mgqyqlmhg8v2cuyncysfuk3r2gg46yl5mrgunjp5plvwkmxtdfjsvwgu45txfp
I'll look into it. Its probably down to a change that adds a id postfix to pr/ branches when your not the author.
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.
Thanks for the patch! I'll download and try it out next time I'm working on this project. I didn't know the large patches would cause issues, but it's good we've identified that. I still need to prep for that discussion and read up based on the other thread. FWIW, when I've tried to puzzle out git over Nostr, I've concluded that full blobs can't/shouldn't live in Nostr events. The events, rather, should point to where the client can download the blob it needs. Blossom might be a good solution for that (though I don't understand Blossom very well yet).
published v1.4.6
Trying it out now, but I get this: > Error: git should set GIT_DIR when remote helper is called > Caused by: > environment variable not found Do I need to set the `GIT_DIR` env var a certain way?
What command are you running?