Enforcing code changes over time
summary
Proposes using version control to restrict linter warnings to lines that actually changed so teams can apply learned rules incrementally, building a filter that queries VCS for modified lines and suppresses unrelated lints. Demonstrates it works but costs about 25% overhead per pull request and can feel like scope creep. Mentions practical tools: linters + VCS filter approach and points to autofixing and codemods as lower-effort alternatives.
AI-written summary · about
chapters (4)
- 0:00Start
- 1:12Version control to the rescue
- 2:30This is not a perfect solution, it might not be for your project.
- 3:15Thank you for listening
