nostr:npub15qydau2hjma6ngxkl2cyar74wzyjshvl65za5k5rl69264ar2exs5cyejr can I get some help?

I'm trying to open a proposal to Alexandria (link below), but it seems the proposal was created with a reference to a non-existent repo event. I can't figure out how to change the upstream repo event in the ngit CLI.

Alexandria:

naddr1qq9yzmr90pskuerjd9ssz9thwden5te0wp6hyurvv4ex2mrp0yhxxmmdqgs06gywary09qmcp2249ztwfq3ue8wxhl2yyp3c39thzp55plvj0sgrqsqqqauej5m80x

My proposal:

nostr:nevent1qqsvec20h56dg0hku0ngxfjna5290pzrqxpcd44j0azq38s3s08ecsqpz3mhxue69uhhyetvv9ujuerpd46hxtnfdupzquqjyy5zww7uq7hehemjt7juf0q0c9rgv6lv8r2yxcxuf0rvcx9evhcjj0

Reply to this note

Please Login to reply.

Discussion

There are a few issues here. As a temporary fix nostr:npub1l5sga6xg72phsz5422ykujprejwud075ggrr3z2hwyrfgr7eylqstegx9z should re-publish the repo by running `ngit init` again. Then new proposal will go to that repo.

As I said there are a few issues.

nostr:npub1m3xdppkd0njmrqe2ma8a6ys39zvgp5k8u22mev8xsnqp4nh80srqhqa5sf is down as the first maintainer in the nostr:npub1l5sga6xg72phsz5422ykujprejwud075ggrr3z2hwyrfgr7eylqstegx9z's repo event but they don't have a repo event at all. ngit and gitworkshop should be robust enough to deal with this but:

1. whilst ngit tags all maintainers in patch events it was only sending it to the first maintainers repo address. this is fixed by nostr:nevent1qqsdjc4dy09n250cw2svfqqdr6tzvkncx3t7gczt4sexa3tup6efffcpz3mhxue69uhhyetvv9ujuerpd46hxtnfdupc9phh

2. the recent change of url structure of gitworkshop.dev to prioritise naddr over d identifiers also caused issues. Links from the repo page https://gitworkshop.dev/r/naddr1qq9yzmr90pskuerjd9sszrthwden5te0dehhxtnvdakqyg8ayz8w3j8jsduq492j39hysg7vnhrtl4zzqcugj4m3q62qlkf8cypsgqqqw7vszahgpn/proposals to the proposal you reference changed the naddr to point to the no-existent repo event, causing an error to displayed. Fixed by nostr:note1nryrg69glqhq0sfw8sfwlpv888whuezwllqt5wfp57etkl7vv3zst5tlh3 now it will always use the naddr from the selected repo event.

you can use the --in-reply-to to specify additional repo naddr pointers.

you can't currently override the ones it auto-selects. I considered saving a selected naddr to git config but its conceivable that for a large repo you might want to send different proposals to specific repositories (like to different working groups of a large repository).

I then thought it would be better to extract naddr's from remote urls once there is a git remote helper. If there were multiple nostr remotes, it could prompt the user to choose.