Oddbean new post about | logout
 What are the purposes of the forks? Do they differ signifcantly? Why not have them as branches of the same repo? 
 We're using the same as branches, with each dev having a fork that they're working on and then making a PR to the source repo for merges.

Just looks neater in the source. 
 Each dev would use the source repo to get the lastest changes. Then use `ngit send` to create proposal (PR equivalent) when they ready to share what they are working on. They can update the proposal with `ngit push` or after a rebase they can use `ngit push --force`. `git merge`  can be used for merging into the master branch to be pushed to the source repo. 
 Okay, looks much better. 😅  I was so confused!
Just prefacing my forks all with "sw_".

https://gitworkshop.dev/repo/sw_gitcitadel 
 It only makes sense to have a nostr repo event for a distinct repository that you would want to receive proposals for or raise issues against. This typically wouldn't be one per developer. 
 Okay, so then it would only need to be the source repos and not my forks. That makes sense. 
 I'm going to keep testing on my fork, tho, to keep the source one neat.

Let me go try to send something again and get you the output. 
 If a user-npub wrote me on Nostr with a bug, how do I turn that into an issue? With some sort of a quote or reply? 
 Hey, nostr:nprofile1qyfhwumn8ghj7un9d3shjtnxxaazu6t09uq3wamnwvaz7tmjv4kxz7fwdehhxarj9e3xzmny9uq32amnwvaz7tmjv4kxz7fwv3sk6atn9e5k7tcqyzsq3hh327t0h2dq6matqn5064cgj2zanl2stkj6s0lg4t2h5dty6xk8zw9  that markdown looks very pretty. I like that. Displays on GitWorkshop better than on GitHub. 
 Thanks. 
 The table, especially. Neat and streamlined.