#GitViaNostr just got 10x easier with a git plugin included in ngit 1.4
clone with a nostr url. any branch prefixed with `pr/` is an open proposal on nostr.
submit it to as a proposal via nostr by pushing a branch with a `pr/` prefix.
see https://gitworkshop.dev for a quick start guide
I'd love feedback
nostr:npub16r0tl8a39hhcrapa03559xahsjqj4s0y6t2n5gpdk64v06jtgekqdkz5pl may be interested dispute his current keyword mute list
Can't wait to play with it!
nostr:npub16r0tl8a39hhcrapa03559xahsjqj4s0y6t2n5gpdk64v06jtgekqdkz5pl zapped ⚡️21,000 sats
nostr:note17qa876qxchnhwu72zhjvx2fhks6q5gpevqdwvj9gft8mr9fakemst8jp8e
👀
nostr:note17qa876qxchnhwu72zhjvx2fhks6q5gpevqdwvj9gft8mr9fakemst8jp8e
where can I find the code for git-remote-nostr?
Do I understand it correctly that when you "push" a pr branch, it publishes the changeset to relays as notes? So there is one maintainer who then updates the original/upstream repo with merged commits?
You got it!
Nice, I like the idea!
I'm sure you already thought about how to handle forks, multiple maintainers, and more? For example, since Git is already content-addressed, I guess we could detect full repo forks by watching for the same hashes to be published to other Git servers/URLs which are initialized (published to nostr) by other npubs. And multiple maintainers wouldn't even need to be solved via Nostr, since their merge permissions can still be managed on Gitea, etc., right?
The repo announcement event can optionally list other maintainers.
A fork, in the tradition sense, can be created by issuing a repo announcement using a different identifier.
Alternatively, using the same identifier by an npub thats not listed as maintainer in the original; but it's polite to use a different identifier / name to avoid confusion.
Interesting, but whenever I see cool applications built on top of Nostr I always end up asking myself: what's the incentive to maintain relays up and running (other than generosity ofc)?
For our side, the incentive is to make the other side (github) do the same
For the other side (github), the incentive is the same incentive they've always had for offering "free" services: collecting whatever data there is to collect, gaining any influence there is to be gained
Good work buddy
