When adding an extension requirement in extension.json, CI would most
probably complain since it does not clone the extension. It has to be
added to the CI configuration:
Add the requirement to the 'dependencies' mapping, then send for review.
Unfortunately one of the CI maintainers would have to approve and deploy it.
As a twist, I wrote a few bits that should make it possible for CI to
automatically process and clone the requirements and thus let us phase
out the central config. But that takes a bit of time to accomplish it
The long story:
MediaWiki extension registration lets one define a requirement upon
other extension/skins. If one writes an extension that extend
VisualEditor, most probably VisualEditor is required, the extension.json
would thus have:
Due to a bug, CI was no more failing when a requirement was not
fulfilled. In fact the extension would not even be enabled when running
That has been fixed via:
From now on, on master branch, CI would fail when a requirement is
missing. Unfortunately, CI does not magically clone the requirements
yet, so you would have to also add them to the CI config (see above).
Antoine "hashar" Musso