I used to be in the camp that cared a lot about formatting, but over time realized that it's more my OCD than any practical reason.
At this point, the only reason why I like consistent code formatting rules is because they prevent bickering between people who have strong opinions on how things should be. When there's a rule, even if people don't like it, they abide by it. When there are no rules, everybody who thinks that there should be rules starts bikeshedding what they ought to be.
But as far as code quality goes, I don't think it matters much.
I'm in that camp that doesn't enforce consistent styling in code or even particularly believe in the value of linting at all! ^_^
I'm pretty much just echoing what others have said, but when I look back at the things that have caused problems / mattered in a codebase, things like formatting are generally ranked an order of magnitude below everything else.
If people care, I'm happy to oblige, but it always seems like a missing the forest for the trees kind of thing.
Because the commit messages, just like email messages, isn't part of the product. They are part of communication between developers. You could as well require people on mailing list to never top-post and always spell correctly, to reduce cognitive load. Some people actually do that, but they are pretty annoying. :)
At this point, the only reason why I like consistent code formatting rules is because they prevent bickering between people who have strong opinions on how things should be. When there's a rule, even if people don't like it, they abide by it. When there are no rules, everybody who thinks that there should be rules starts bikeshedding what they ought to be.
But as far as code quality goes, I don't think it matters much.