Automatic Checks for the People
summary
Automatic enforcement of style and correctness uses pre-commit hooks for fast, fixable checks and CI jobs for heavier checks; concrete tools named are black for deterministic formatting, isort/import sorting, prospector and bandit for linting/security, and terraform validate for infra. The workflow runs quick formatters on commit, repeats hooks in CI, and runs slow checks in parallel so build time stays acceptable. Practical options are a one-time repo-wide reformat or the incremental “Boy Scout” approach; pre-commit lists ~200+ available hooks.
AI-written summary · about
chapters (5)
- 0:00Introduction and background
- 6:58Pre-commit framework explained
- 14:17CI as second line of defense
- 19:15Adding checks to legacy projects
- 22:16Q&A session
related talks
30mLearn how to never commit $%@ to Git
44mStop fighting useless battles: automate code style, architecture compliance
08mAutomated Checks Before Publishing Open Source, a Few Years La...
31mCode Style and Violence
25mcode review is too late for code quality
16mClean code is no longer a myth
07mMake Linting Great Again
42mBeyond spell checking - what else can we check automatically?