right but on a nostr event the pub key would have to match the signature. or the relays would reject it. So unless everyone that is able to commit to the repo shares a keypair that wont work i don't think.

I did this by having a repo publish event and then everything related to that repo has an e tag referencing the event. And at the client level you handle the collaborators, by ignoring events that arent published by pub keys with permissions.

Reply to this note

Please Login to reply.

Discussion

Good feedback. I should rename the title a bit to make it clearer

The main thing on the nostr side will be references to actual git repos. There wont be commits, but there might be patches

So it's more like a git discovery and realtime update NIP, than git over nostr

Full git over nostr would be more complex and could be another nip. Possibly this would lay the ground work.

Possibly I could extend this to commits too. I'd like to get a working implementation first, then evaluate what's practical

This is the way

Having nostr bootstrap nostr is a powerful signal.

🤙

So repos would run a dumb git server and nostr would act as the issue tracker?

commit tracker