News for hackers. Stuff that matters.
Re:Resistance against London tube map commit history (a.k.a.... by lolinder on Wednesday May 01, 2024 @07:51AM (#40222002)
That's why they said this:

> If you make a meandering series of commits during development, squash them for the PR. But please, please do not squash the entire feature upon merge.

I typically turn my PRs into a series of buildable and testable commits. I also put a lot of work into making those commits tell a useful story to the reviewer and to anyone doing git blame later, and squashing them all into one commit undoes that work.

Re:Resistance against London tube map commit history (a.k.a.... by dllthomas on Wednesday May 01, 2024 @12:44PM (#40225749)
Buildable and testable, but notably sometimes not formatted or linted, when (atypically but not rarely) the semantic change is much easier to understand separated from the superficial changes it motivates in the context of the formatting/linting rules of the project.
Re:Resistance against London tube map commit history (a.k.a.... by lolinder on Wednesday May 01, 2024 @07:53PM (#40231104)
Yep. And in a similar vein, not squashing allows you to separate a file move from changes to it so that git can track the move.