Oddbean new post about login | logout I didn't really know how to use it, so I cloned the source repo and my fork. I guess I submit patches from my fork to the source and then accept them on the other side, somehow?
If you want to submit a patch from the source repo you can. Submit the patch using `ngit send`. Other people can comment.
To accept the patch as-is, use `ngit list` to either checkout a branch with the patch that can be merged with `git merge` or apply the patch directly to the tip of your current branch (best done from master).
Once applied / merge you can mark it as merged on gitworkshop
We only submit from forks, over PRs. So far. So that everyone can review and comment before the merge, and to keep the source repo neater. Trying to figure out how to use the patch stuff. What exactly is the difference?
a proposal (created with `ngit create`) is like a PR which lives on nostr instead of a fork. Anyone on nostr can comment on it before it is merged. They can view proposals with `ngit list` and check them out as branches (like you can with a PR)
I think I should write a detailed guide as I guess the high level overview of the commands are not sufficient
Would probably help more people to use it.
Yes. In could also do some 30 second screencasts to show how quick and easy it is
I'm also thinking about adding a git remote helper so that you can use more native git commands like `git branch -r` to list proposals
Like a throughput to git?
Remote helpers allow git functions like fetch and push to work over other protocols like ssh or https or nostr. The nostr protocol could proxy requests to the 'clone' address specified in the events and then make proposals on nostr act as remote branches.
the getting started guides on gitworkshop.dev are sufficient at this stage. If anyone is struggling. feel free to repoen this issue