So that atomic changes are consolidated in a single commit/PR.

Sometimes, the flow for a single feature A: - commit change AA - commit change AB - fix change in AA - extend AB

In this case, until merged into main/master and to reduce noise for the reviewer (especially if using a code review each commit type process), its best to squash all commits into a single "feature A".