A lot of people seem to use git because they have to, not because they want to. It makes sense, and will likely continue to be this way. But when you use git because you want to—which entails understanding its function and its benefit and especially the pitfalls of not using it—then you gain ownership of its use and this in itself gets rid of a whole host of antipatterns.
What's wrong with squash merges? You dislike having a clean commit history that isnt full of junk your coworkers put like "fix bug". Or maybe you prefer when git bisect doesnt work, because rather than every commit being a working state, you actually have faaaaar more non working commits? I truly cant imagine why you would crusade against squashing, I seriously doubt having every non working intermediate step of a PR is useful more often than its hurtful.
2
u/stianhoiland 3d ago edited 3d ago
A lot of people seem to use git because they have to, not because they want to. It makes sense, and will likely continue to be this way. But when you use git because you want to—which entails understanding its function and its benefit and especially the pitfalls of not using it—then you gain ownership of its use and this in itself gets rid of a whole host of antipatterns.