I work in a team of about 10 at a large company and it's convention to squash. The alternative is turning a potentially very messy history into something we'd c

I work in a team of about 10 at a large company and it's convention to squash. The alternative is turning a potentially very messy history into something we'd care to look at two months from now. This doesn't seem worthwhile, especially since you now have a situation where some commits on master are intermediate, unshippable states. What am I missing?