This will alert us to things going wrong quickly. Hopefully. (Yes, there's a risk of noise, but there should be 0 of these, anyway.)
Version: unspecified
Severity: enhancement
This will alert us to things going wrong quickly. Hopefully. (Yes, there's a risk of noise, but there should be 0 of these, anyway.)
Version: unspecified
Severity: enhancement
The CVNBot software used for #cvn-sw, #cvn-commons, #cvn-meta etc. can't provide this because of limitations in the source feed, irc.wikimedia.org, which doesn't expose revision change tags.
Looks like realistically the fast way to make this happen is probably a little nodejs project ran from tool labs that polls wikis using one of these approaches:
Pros:
Cons:
1b) Alternative: Like #1a, but do the changetag retrieval via SQL query to labsdb instead of API request.
Pros:
Cons:
Pros:
Cons:
Pros:
Cons:
As I said in IRC, option 3 seems sanest to me, but that's not really my call as I'm not the one that'll write it. :-)
Went with approach #3, it's a python script run under the 'wm-ve-needcheck-reporter' service user in tool labs. Cron set up to run every day at 16:30 (UTC).
(In reply to Elitre from comment #3)
Should vepawns edits be tracked as well?
Perhaps we should have a separate bug for this - it sounds like a good idea to mark edits which add new pawn characters to the page as needcheck
@Alex, that filter doesn't seem to be catching anything, I have no idea if it's still functional or not, that's why I asked.
The tag vepawns, i.e. : https://en.wikipedia.org/w/index.php?title=Special:RecentChanges&tagfilter=vepawns .
(In reply to Elitre from comment #7)
The tag vepawns, i.e. :
https://en.wikipedia.org/w/index.php?title=Special:
RecentChanges&tagfilter=vepawns .
That's not done by VisualEditor; these must be a local AbuseFilter written by the community…