DEV TOOLS Signal 136
Accepting a messy git history
GitHub's release of stacked pull requests has reignited this debate, highlighting that tooling is increasingly accommodating less rigid git workflows. For engineers, this suggests that enforcing strict rebasing policies may be unsustainable without high discipline, making squash merges and accepting a messier main branch a more practical default.
Written by elseif from the cluster below · every claim links back to a sourceThe three things worth knowing
GitHub's introduction of stacked pull requests is celebrated by developers who commit often, while those who prefer careful rebasing question the utility.
Debate continues over whether to preserve detailed commit histories via merge commits or to use squash merges for a cleaner main branch.
The author concludes that accepting a messy history is often more resilient for large teams because strict rebasing discipline is difficult to maintain.
THE CLUSTER