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.