A wikibase repository typically also functions as a wikibase client (having itself as the connected repo).
In this setup, dispatchChanges should post ChangeNotificationJobns to the local wiki's (the repo's) JobQueue, in addition to the wikis listed in localClientDatabases.
Then we could enable this on wikidata.org, when we have not yet.
| Subject | Repo | Branch | Lines +/- | |
|---|---|---|---|---|
| If the repo is a client, it should dispatch changes to itself. | mediawiki/extensions/Wikibase | master | +26 -5 |
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Invalid | None | T108944 [Epic] Improve change dispatching | |||
| Resolved | daniel | T113606 [Task] dispatchChanges should dispatch to local wiki if client functionality is enabled on the repo |
Change 367325 had a related patch set uploaded (by Hoo man; owner: Daniel Kinzler):
[mediawiki/extensions/Wikibase@master] If the repo is a client, it should dispatch changes to itself.
Change 367325 merged by jenkins-bot:
[mediawiki/extensions/Wikibase@master] If the repo is a client, it should dispatch changes to itself.
Should we resolve it? I can't see any configs related to enabling it in wikidata so I'm guessing it gets automatically enabled?
Yea, this is done.
It's not optional and needs no config.
It won't make any difference in production, since we already had wikidatawiki configured as a client, and we are regularly dispatching changes to wikidatawiki.