When folks want to add a new extension, some folks are already confident doing it, but we should document for folks new to PatchDemo.
AC:
| Title | Reference | Author | Source Branch | Dest Branch | |
|---|---|---|---|---|---|
| Add documentation for adding new extensions | repos/test-platform/catalyst/patchdemo!190 | kindrobot | T400921-new-ext-docs | main |
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | SDunlap | T400921 Document adding a new extension to PatchDemo | |||
| Duplicate | SDunlap | T401416 Add ReaderExperiments to PatchDemo |
Rough steps:
In ci-charts:
In patchdemo:
In catalyst-api
nothing
in wiki-repos-pool
nothing
- add repo to repository-lists/wikimedia.yaml if it is deployed on production wikis
It might be worth noting that this step may be more applicable if the extension is enabled on a large number/large proportion of production wikis, rather than (e.g.) just one or two.
(I can't think of many citations for this off the top of my head, but a recent semi-related example was ext:Wikibase — which was originally included within the Wikimedia preset when it was added to Patch demo, but was later removed from the preset due to causing problems for some non-Wikibase developers due to having different search-bar behaviours. xref T372960: Add Wikibase Repository and Client extensions, T393806: Wikibase breaks desktop search on default patchdemo installs)
kindrobot opened https://gitlab.wikimedia.org/repos/test-platform/catalyst/patchdemo/-/merge_requests/190
Add documentation for adding new extensions
Actually, there are quite a few. I tried to collect them, but may have missed some:
Some of these like Flow or FlaggedRevs are risky, but others like SandboxLink or MediaSearch probably wouldn’t cause many issues; still, none of them are included in the Wikimedia preset.
kindrobot merged https://gitlab.wikimedia.org/repos/test-platform/catalyst/patchdemo/-/merge_requests/190
Add documentation for adding new extensions