The simplest possible git collaboration flows that have a chance of working.
Discussion
This is something I very much look forward to see happening.
Do you have a good resource for using patches in git works flows because I have never had to use that, mostly clone, make changes, commit and submit pr
https://git-send-email.io is a good resource, but it can be as simple as:
git format-patch HEAD
And sending it over any medium you want (signal, etc)
OK, I get it. How then would replies to a patch denote line of code they're discussing?
I don't understand
"Their root doesn't have to be a kind:1621 issue, but also a kind:1617 patch event."