I disagreed with you up to this point: > Of course if you have developers that don't do that and instead merge dozens of commits that just say wip, wip, wip, l

I disagreed with you up to this point: > Of course if you have developers that don't do that and instead merge dozens of commits that just say wip, wip, wip, lol, fml, wip, wip, lol, yolo and you can't fire them or get them to change, then squash merges ftw. Yes, any large organization has plenty of devs who all have their own style and preferences, for better or worse. Whoever demands they all bend to the one true way is a fascist (lol not really but you know). Just set up your CI/CD in such a way that PRs with weird git logs get squashed into one pretty message, preferably the PR description since other devs have to review the PR it's often given more effort. Set it up so that if things weren't formatted the "right way" they get auto-formatted or a test fails and the dev says "ah, I have to run that one task and then update the PR". I don't think a big organization is going to scale with developer "evangelists" demanding people write their commits a certain way either. conventionalcommits.org was the worst. I worked at one "big co" that tried to get devs to do this. Even after we had been doing it for a while, nobody ever went back to look at the history in such a way that it was worth it. We ended up throwing in the towel rather than the company trying to get all other teams to do it.