Lukewarm take: Editors automatically formatting on save are horrible when collaborating on software.
Because you will inevitably end up with commits containing both meaningful, intended changes and "abide to some styleguide" meaningless changes on whitespace and string delimiters.
And the Reviewer of your PR has to read through all of that and make sense of it. THAT is waste of resources.
@schnittchen counterpoint: your repository should have a defined style and only accept commits that comply with that style. That way, format-on-save becomes really useful
@schnittchen nah, you can just format everything in one big commit. It shouldn't even fuck up your history too much
@noiob if you're only one or two ppl on the team and it's a very small codebase
@noiob that requires all existing code to be already in shape, which in my years of experience is extremely rately the case.
Once all linting is done at some point, the problem becomes trivial: all it needs is some check that prevents unlinted code to be committed or integrated, which could be done via CI or git hook.