Replying to Avatar DanConwayDev

With ngit, you dont have to use the branch-merge-model. Its built to be an accessable tool which can fit into a range of workflows. For example with `ngit send` you can create patches from selected commits. `ngit list` can apply them.

I love that we open protocols like git and nostr, there can be tools like n34 which hone in on a specific workflow and do a great job at making it smooth.
Avatar
DanConwayDev 4mo ago

n34 also works good in conjunction with ngit. Clone a repository using a nostr:// and you'll get the repository state through nostr and the git data from the git servers the maintainers list vianostrl, but you can use n34 for browsing, applying and sending patches for the repo.

Reply to this note

Please Login to reply.

Discussion

Avatar
DanConwayDev 4mo ago

That's not even mentioning the totally cool n34 feature of being able to fire off issues from the command line.

Avatar
Awiteb 4mo ago

Exactly, you can mix them and make something you comfortable with, like using ngit for sending and fetching but n34 for issues and reviewing patches.