The fact that not many people know this unfortunately leads to a side-effect that it is less widely supported by third-party tooling around git. In terms of si

The fact that not many people know this unfortunately leads to a side-effect that it is less widely supported by third-party tooling around git. In terms of simplicity (for example, 'git revert x' is natural-language-like and expresses the intent and meaning), and also in terms of tooling compatibility, that generally leads me to prefer squash commits. One other thing that squash commits can enable is a sense of developer freedom within their branch(es). There's no need to keep the history super hygienic within each branch; there can be plenty of reverts, experimental commits, etc; the eventual merged product ends up looking clean regardless.