Operator: DannyS712 ( talk · contribs · SUL · edit count · logs · page moves · block log · rights log · ANI search)
Time filed: 06:20, Sunday, December 1, 2019 ( UTC)
Automatic, Supervised, or Manual: automatic
Programming language(s): Javascript
Source code available: will adapt User:DannyS712 test/Flagged revs patroller.js for toolforge
Function overview: Automatically accept pending changes that have no net change
Links to relevant discussions (where appropriate): n/a
Edit period(s): No edits outside of user space
Estimated number of pages affected: Lots patrolled (article and project namespaces only)
Exclusion compliant (Yes/No): N/a
Already has a bot flag (Yes/No): No, but only the pending change reviewer flag is needed (there is no ratelimit on patrolling to worry about)
Function details: Sometimes, there are 2 or more pending changes to a page that leave the page in the same state it was (i.e. result in no "net" change). This can happen if an IP/unconfirmed editor reverts another, or for other reasons (see
phab:T234743 and
phab:T233561 for some issues). This bot would automatically accept the final state, reducing the pages in the backlog. While this only saves an actual reviewer a few seconds, it allows users with autoreview
but not review
rights to have their edits shown immediately. A similar task has been run a few times on enwikibooks, which has a more complicated flagged-revs setup, and has been triggered manually. This task, however, would be triggered automatically (probably every 15 minutes). To be clear, it only "accepts" a version that is identical to the last accepted version. Search for "no net change" at
[1] to see examples that would be patrolled.
There are a lot of unknowns in here. Where it was discussed. How many pages will be affected. How often this bot will run. Is there any information other than "this is sort of maybe a problem that might save a little bit of time"? Primefac ( talk) 16:32, 1 December 2019 (UTC) reply
Approved. Primefac ( talk) 18:40, 30 December 2019 (UTC) reply
Operator: DannyS712 ( talk · contribs · SUL · edit count · logs · page moves · block log · rights log · ANI search)
Time filed: 06:20, Sunday, December 1, 2019 ( UTC)
Automatic, Supervised, or Manual: automatic
Programming language(s): Javascript
Source code available: will adapt User:DannyS712 test/Flagged revs patroller.js for toolforge
Function overview: Automatically accept pending changes that have no net change
Links to relevant discussions (where appropriate): n/a
Edit period(s): No edits outside of user space
Estimated number of pages affected: Lots patrolled (article and project namespaces only)
Exclusion compliant (Yes/No): N/a
Already has a bot flag (Yes/No): No, but only the pending change reviewer flag is needed (there is no ratelimit on patrolling to worry about)
Function details: Sometimes, there are 2 or more pending changes to a page that leave the page in the same state it was (i.e. result in no "net" change). This can happen if an IP/unconfirmed editor reverts another, or for other reasons (see
phab:T234743 and
phab:T233561 for some issues). This bot would automatically accept the final state, reducing the pages in the backlog. While this only saves an actual reviewer a few seconds, it allows users with autoreview
but not review
rights to have their edits shown immediately. A similar task has been run a few times on enwikibooks, which has a more complicated flagged-revs setup, and has been triggered manually. This task, however, would be triggered automatically (probably every 15 minutes). To be clear, it only "accepts" a version that is identical to the last accepted version. Search for "no net change" at
[1] to see examples that would be patrolled.
There are a lot of unknowns in here. Where it was discussed. How many pages will be affected. How often this bot will run. Is there any information other than "this is sort of maybe a problem that might save a little bit of time"? Primefac ( talk) 16:32, 1 December 2019 (UTC) reply
Approved. Primefac ( talk) 18:40, 30 December 2019 (UTC) reply