3 ms·
Keeping the commit as the unit of change allows you to orchestrate with a single PR. The commit is the change, the PR is the go button. > In the rare case you
by mattpallissard 3y ago
Keeping the commit as the unit of change allows you to orchestrate with a single PR. The commit is the change, the PR is the go button.
> In the rare case you have 3 steps in that PR of 23 commits
I'd have 3 commits in this case.
It's not rare at all when you have code, charts, terrform, and scripts housed in a single repo. But even if you're just touching code some changes make sense to go out at the same time.
Personally, I feel that the use case for squash is when there are many WIP commits. Those could be avoided with the use of --amend, or --fixup, or cherry picking without a commit, etc.