Practise the standard verbs for configuring linter rules consistently.
0 / 5 completed
1 / 5
Fill in: 'We ___ a shared linter config across every repo, rather than letting each team invent rules nobody else actually follows.'
We 'maintain a config' — the standard, simple collocation for keeping linter rules consistent across repos. The other options are less idiomatic here.
2 / 5
Fill in: 'Disabling a rule locally without a comment can ___ the next reader confused about why it's actually turned off there.'
We say an unexplained disable will 'leave' the next reader confused — the standard, natural collocation for the resulting ambiguity. The other options aren't idiomatic here.
3 / 5
Fill in: 'We ___ every new rule as a warning before making it an error, rather than breaking a hundred files nobody's actually had time to fix.'
We 'introduce a rule' — the standard, simple collocation for phasing in a new linter rule gradually. The other options are less idiomatic here.
4 / 5
Fill in: 'We ___ every rule change against CI on a sample repo, rather than rolling out a config nobody's actually verified doesn't break builds.'
We 'validate a change' — the standard, simple collocation for testing a linter config update before rollout. The other options are less idiomatic here.
5 / 5
Fill in: 'We ___ suppressed rules quarterly across the codebase, rather than letting exceptions pile up that nobody's actually revisited.'
We 'review suppressed rules' — the standard, simple collocation for periodically re-checking disabled linter rules. The other options aren't idiomatic here.