Problem Statement
When would you enforce squash merging in a repository and what are the trade-offs?
Explanation
Enforce squash to keep a clean, one-commit-per-PR history and easy revert. Trade-offs: lose granular interim commits and bisect fidelity; mitigate by writing a thorough squash message and linking PR.
Practice Sets
This question appears in the following practice sets: