4 ms·
I do squash merges but keep the feature branches. So after determining that I made a change as part of a big pull request, I can then look at the commit/blame h
by johnsbrayton 3y ago
I do squash merges but keep the feature branches. So after determining that I made a change as part of a big pull request, I can then look at the commit/blame history for the pull request source branch if necessary.
- matijsvzuijlen 3y agoThis means having to keep these branches around cluttering up everything, and makes git bisect a lot more complicated.
- mvdtnz 3y agoI'm guessing you don't work on large projects. This would create an outrageous amount of noise in a busy repository.