Accepting a messy git history
Summary
The article surveys debates over git history patterns: whether to commit often or to rebase for a clean history, and how squash merges affect traceability on the main branch. It uses stacked PRs and real-world team discussions to illustrate governance challenges and the trade-offs between readability and preserving history, especially in larger organizations.