3 ms·

I religiously squash my commits for each merged pull request. I seems like madness any other way to me... why have a bigger granularity than a single merge com

I religiously squash my commits for each merged pull request. I seems like madness any other way to me... why have a bigger granularity than a single merge commit?

adrianN 6y ago
Granularity helps with bisecting issues.
- bJGVygG7MQVF8c 6y ago
  Yes. But also: Granularity undermines the effectiveness of bisecting when your commits aren't ACID. These conversations are so often tedious and repetitive largely because engineers seem incapable or unwilling to apply systems thinking to development practices.
- jdmoreira 6y ago
  at least in github after you find the squash commit equivalent to the PR you can restore the branch and bisect the rest in there. This is much faster!
DougBTX 6y ago
Interesting, it seems like madness to me to have it the other way around. Why bother with a merge commit if all the changes are squashed into one anyway? Why not just fast forward merge as if it was a commit directly to the main development branch?