Unless we're talking about different workflows, squashing works great. In my team, we merge squash our PRs, having a guideline that they should be a small incr

Unless we're talking about different workflows, squashing works great. In my team, we merge squash our PRs, having a guideline that they should be a small increment. Here's what happrns: - when you checkout a commit, you are guaranteed to have a version that was reviewed by a person and validated by ci/cd - most commits have chsnegs with substance, instead of "log", "debug", etc Without squash, a person can push 3 commits to a feature branch, ci/cd says the last commit is OK, it gets merged, and you may get 2 commits that don't compile or cause a very basic runtime error due to some typo or whatever. (not that it could not be solved with due diligence, but that comes with higher effort too) How do you assure working commits and avoid noise without either squash or rebase?