A strategy I have used is: - only lint the files that have changed - only apply lint rules that can be auto-fixed
This usually takes less than a second (short enough that you can't really tell the difference) and the developer doesn't have to do anything .
Yes. I work in a codebase that's 30GB checked out. It takes a long time to run our automated checks. That's why they happen on the server, when I make a pull request.
The upshot is the same: it doesn't go to master until checks pass. But who gives a shit about what I'm committing locally? I reserve the right to save my work even if things aren't compiling. You (my teammate) won't see it anyway, it's all locally on my machine. Why do you care?