Comment Comment by diek > destroying Commit information just to keep the graph tidy is a bad idea in my opinionThe commit information I see when telling teams to squash their branches on merge is not valuable.* "fixing whitespace" * "incorporate review comments" * "fix broken test" * "fix other broken test"(note, the broken tests were broken by the changes in the PR)As soon as that PR is merged those commits are worthless. And there are branches with dozens of those "fixing X" commits that would otherwise pollute the commit graph. parent diek 3 years ago
The commit information I see when telling teams to squash their branches on merge is not valuable.
* "fixing whitespace" * "incorporate review comments" * "fix broken test" * "fix other broken test"
(note, the broken tests were broken by the changes in the PR)
As soon as that PR is merged those commits are worthless. And there are branches with dozens of those "fixing X" commits that would otherwise pollute the commit graph.