Linting best practices
Last updated
Last updated
Linters look at a program's soruce code and find problems automatically.
They are a common feature of pull request automations because they ensure that "obvious" bugs do not make it to PROD
Code reviewers leave little comments on the code called "nits" that the team can ignore until broader reviews.
Nits are helpful as future references but prevent blocking important changes
Tools that help apply code style rules based on the style guide your team has chosen automatically
Developers should never wait for a human reviewer to let them know if their code is linted and styled correctly
Cheap and convenient to run linting and formatting within CI steps
Even better solution in CI:
Any team with more than one developer working in the same codebase should setup a linter to catch obvious bugs
DeepSource pricing can be found here: