4 ms·
> Why do you need to squash & merge literally every PR? Why not use squash & merge when appropriate and rebase & merge otherwise? "When appropriate" is the key
by alphazard 3y ago
> Why do you need to squash & merge literally every PR? Why not use squash & merge when appropriate and rebase & merge otherwise?
"When appropriate" is the key here. That's asking people to make a decision, take on additional cognitive load, which does not have a clear deliverable or success criteria. In practice the default is what happens.
- burntsushi 3y agoWe need to make decisions about code and maintainability all the time. I don't see why this is any different.
- rokkitmensch 3y agoEvery opportunity to eliminate cognitive overhead is a win for the team. As I say to my children on the reg, "What's the best way to clean up a mess? Don't make it in the first place."
- brayhite 3y agoAs my children repeatedly prove: one person’s “not a mess” is another person’s disorganized chaos.
- burntsushi 3y agoTelling my child not to make a mess so he can avoid cleaning it up would not be an effective tactic at anything other than acting smug. You're presupposing that this decision is worth making for programmers in the first place. I don't see why that ought to be true.