Hacker News Reader

You could use something like https://github.com/typicode/husky to prevent a push if the linter fails.

My (small) issue with git hooks, is that they need be installed everywhere for them to be 100% enforced. Works fine for small teams, but doesn’t scale that well beyond that.

You make the hooks as part of the CI process. That's where something like husky can come in. We do this on my team.

If you're trying to enforce something locally you can definitely enforce it on CI automatically. Once people realized their PRs were failing due to linting issues they started checking them locally as well.

This is what we use. Husky runs linters on pre-commit to ensure everything is linted going into the repo.

We added linter checks to our Travis CI config. It helps flag the PRs that don't pass the linter.

The problem I've seen is that the error message isn't obvious. It just says that the "build failed", which sounds more like a compilation error than a lint problem.

that's what github actions are for.