4 ms·
By doing this, you break commit atomicity and make bisects hell. Please don’t do this. Commits aren’t perfect at first for sure, but they should be by the time
by trashburger 2y ago
By doing this, you break commit atomicity and make bisects hell. Please don’t do this. Commits aren’t perfect at first for sure, but they should be by the time you make them reviewable.
- snatchpiesinger 2y agoIt's fine to break commit atomicity on feature branches. You can use git bisect --first-parent on you development/master branch.
- trashburger 2y agoI completely disagree. In doing so you lose all visibility into the components and gradual evolution of the code that atomic commits provide. Same thing with squashing (which is just the worst).