With nostr:nprofile1qyd8wumn8ghj7urewfsk66ty9enxjct5dfskvtnrdakj7qgmwaehxw309aex2mrp0yh8wetnw3jhymnzw33jucm0d5hsz9mhwden5te0we5hgmmj9ehx7um5wgcjucm0d5hsqgpm7rrrljungc6q0tuh5hj7ue863q73qlheu4vywtzwhx42a7j9n5a3m46r 's GitStr you can now send a git patch to Amethyst through Nostr's relays and fully avoid GitHub.

Instructions here: https://github.com/fiatjaf/gitstr

Dashboard: https://patch34.pages.dev/naddr1qvzqqqrhnypzq3svyhng9ld8sv44950j957j9vchdktj7cxumsep9mvvjthc2pjuqqyxzmt9w358jum5nw4h94

NIP: https://github.com/nostr-protocol/nips/pull/997

Reply to this note

Please Login to reply.

Discussion

Sounds big!!

nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6 "GitStr"?

*grumbles* I'll allow it

It's fine because it's for programmers.

The name matching the command line is king to me.

👏👏👏👏👏

Amazing

Do you think it will increase overhead to accept changes both via PR's and GitStr? Or is it always better (more robust) to accept both?

It will probably increase the work. But nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6 did a great job simplifying the git bullshit for us mere mortals.

It will be interesting to see which workflow nostr devs will prefer once we release our solution to replace github. Not that it will be mutually exclusive at all with the nostrocket&GitStr way but the way things are developing it seems there will be at least two major ways to maintain projects.

Well, devs in general. Sovereign code isn't limited to nostr projects of course.

Good to see multiple implementations and it doesn't ideally matter as long as where the code is depends simply on the right git incantation

Ironically hosted on GitHub.

There's a lot more to GitHub than this.

GitHub is massive.

Not really.

Well. I can't argue with that.

oh this is cool ^^

very cool to see people used GitStr to send patches for the latest release