I'll do this stuff for myself in a long-lived branch to keep rebasing and cherry-picking on the table. I don't see the value for small changes, just squash. I

I'll do this stuff for myself in a long-lived branch to keep rebasing and cherry-picking on the table. I don't see the value for small changes, just squash. I also don't see the value in a PR-based workflow, as your team's PR practices should have sufficient context without asking everyone to rewrite history. I also don't really believe that devs can reliably retcon atomic commits that compile using just git commands. You make a nice commit for the new file but forget that it has a dependency in another new file. Or you remember the dependency and painstakingly add -p the functions necessary for the commit, but forget one variable definition that was in a chunk at the top of the file.