3 ms·
When you squash merge on github the new commit references the old PR. If you don't delete branches on merge you would keep the commit history on that branch, bu
by 91edec 3y ago
When you squash merge on github the new commit references the old PR. If you don't delete branches on merge you would keep the commit history on that branch, but then you have to battle with branchs persisting forever.
- cplusplusfellow 3y agoBranches are mostly free, so this isn’t a problem if they are properly named. “try-again-something5” doesn’t cut it but “$ticket-at-least-five-words-here” does.
- TheCleric 3y agoBranches are not cognitively free. Searching through the haystack of hundreds of branches to find a particular needle is a pain.
- cplusplusfellow 3y agoYou’re translating the problem from : searching through branches that are named according to their ticket and what they are meant to accomplish to: complex and not-context-free git bisect.