Spaces vs tabs, where to put braces, how deep to make indentation. All these are things that developers have argued about since the first programming languages. They also don’t really matter so arguing about them is a waste of time. Most widely used languages have mature auto formatting tools that enforce a specific style. Pick one for your language, start with the default configuration, and build a checker into your CI workflow.

Introducing this can cause lots of changes to your codebase. This is annoying but it’s better to do a series of formatting change only PRs that don’t change behaviour so are safe to apply. If you don’t do this then a one line logic change PR in a largish file that isn’t auto formatted yet can get lost in the diff when it is auto formatted.

Arguments about formatting style move to PRs against the auto formatter configuration. There tends to be a lot less of these when there is an auto formatter which is another benefit of introducing it. It’s easy to configure your editor or git hooks to run the auto format tool on save or on commit so it’s completely automated.

If your team isn’t using an auto-formatter then why not?