Oddbean new post about | logout
▲ ▼
DanConwayDev | 7 months ago (raw) | root | parent | reply | flag 
 If you want to submit a patch from the source repo you can. Submit the patch using `ngit send`. Other people can comment.
▲ ▼
DanConwayDev | 7 months ago (raw) | root | parent | reply | flag 
 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).
▲ ▼
DanConwayDev | 7 months ago (raw) | root | parent | reply | flag 
 Once applied / merge you can mark it as merged on gitworkshop
▲ ▼
Silberengel | 7 months ago (raw) | root | parent | reply | flag +1 
 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?
▲ ▼
DanConwayDev | 7 months ago (raw) | root | parent | reply | flag 
 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)