From the actionables on https://wikitech.wikimedia.org/wiki/Incident_documentation/20200207-wikidata
.. and again from https://wikitech.wikimedia.org/wiki/Incident_documentation/20200703-Lilypond_down (after T257079).
From the actionables on https://wikitech.wikimedia.org/wiki/Incident_documentation/20200207-wikidata
.. and again from https://wikitech.wikimedia.org/wiki/Incident_documentation/20200703-Lilypond_down (after T257079).
In theory you can get every possible config option by reading through extension.json and DefaultSettings.php. But we often stage new config settings before deployment, so the proposed linter would need to be able to work around that.
@Krinkle's codesearch-based script might work nicely in CI (maybe with some false positive exclusion list) because as soon as something is merged in master, it'll be in search so it can be added to mediawiki-config.
Change 616641 had a related patch set uploaded (by Krinkle; owner: Krinkle):
[mediawiki/tools/code-utils@master] wmf-config-wg-vars.js: Add README
Change 616641 merged by Krinkle:
[mediawiki/tools/code-utils@master] wmf-config-wg-vars.js: Add README
Change 616643 had a related patch set uploaded (by Krinkle; owner: Krinkle):
[mediawiki/tools/code-utils@master] wmf-config-wg-vars.js: Use the '/deployed' preset for Code search
Change 616643 merged by Krinkle:
[mediawiki/tools/code-utils@master] wmf-config-wg-vars.js: Use the '/deployed' preset for Code search