[cwilkes]

I don’t understand the dislike of rebase — do you want hundreds of commits that say “linter fix” and “reformatting”?

If there’s commits like “fixed off by one issue in refactor” then it should be a comment in the code so that future will explorers won’t make the same mistake.

Rebase by itself isn’t bad, it just has to contain a good description of what was done and why.

Edit: after posting I realize that I confounded rebase and squash — which is kind of ingrained in my head as that’s how I use GitHub to merge PRs.

[Double_a_92]

They are better than one single commit with 100s of changed files. Especially when you are debugging things and want to know why exactly some line was changed in that way and by whom.