Practise the standard verbs for sharing ESLint config across repos.
0 / 5 completed
1 / 5
Fill in: 'We ___ a shared ESLint config as its own package so every repo in the org enforces the same rules.'
We 'publish a package' — the standard, simple collocation for releasing a reusable config module. The other options are less idiomatic here.
2 / 5
Fill in: 'A repo overriding half the shared rules can ___ inconsistent style creeping back in project by project.'
We say local overrides will 'allow' inconsistency back in — the standard, natural collocation here. The other options aren't idiomatic here.
3 / 5
Fill in: 'We ___ the shared config in each project's own eslintrc rather than copy-pasting the rule list everywhere.'
We 'extend a config' — the standard, established ESLint collocation for inheriting from a base rule set. The other options aren't the recognised term here.
4 / 5
Fill in: 'We ___ the shared config's version across repos in CI so nobody drifts onto stale, unpatched rules.'
We 'pin' a version — the standard, established collocation for locking a dependency to an exact number. The other options aren't the recognised term here.
5 / 5
Fill in: 'We ___ a new rule into the shared config gradually, as a warning first, before making it an error everywhere.'
We 'roll out' a change — the standard collocation for introducing something incrementally across many consumers. The other options aren't idiomatic here.