Wikimedia Meta-Wiki

MediaWiki talk:XTools-AutoEdits.json

This is an archived version of this page, as edited by 1234qwer1234qwer4 (talk | contribs) at 02:57, 13 August 2025 (→IABotManagementConsole [1.3]: Closed - with ReportSolver). It may differ significantly from the current version.

Latest comment: 13 days ago by 1234qwer1234qwer4 in topic IABotManagementConsole [1.3]
Learn more about this page
XTools AutoEdits configuration
This page is used to request changes to configuration file that controls the XTools AutoEdits tool.

Only tools that are widely used should be included. Every tool added will slow down XTools a tiny bit more, so please be diligent and ensure the list doesn't become overly exhaustive.

Administrator instructions
Guidelines
  • Remember that only tools that are regularly and widely used should be included. Every addition here slows down the queries a tiny bit more. We cannot include any and every tool ever made. Also note that very similar tools can be combined to improve performance; for example the "delsort" tool for en.wikipedia includes multiple tools. You make the judgement call, but feel free to ask for help from other maintainers here if you are unsure.
  • Test your changes before saving. Do this by first updating MediaWiki:XTools-AutoEdits.json/sandbox with the desired changes. Then, login to XTools and append ?usesandbox=1 to any XTools AutoEdits result page to force it to use the sandbox. The easiest way is to test against accounts that have made edits using the tool you're trying to add, and look for contributions using only that tool. The requester should have shared example diffs.

    For example, if you wanted to add the tool "My Fun Tool" to de.wikipedia, which you know has been used by User:Example: Add the definition to the sandbox config, then load the contributions page for just that user and tool, as with:

    https://xtools.wmflabs.org/autoedits-contributions/de.wikipedia.org/Example?tool=My+Fun+Tool&usesandbox=1

    From here you can see if the qualifying edits show up. Compare with production (without ?usesandbox=1) as necessary. While you can use the sandbox on a normal /autoedits result page, loading just /autoedits-contributions is significantly faster.

    Note also that the ?usesandbox=1 option will bypass caching, so any changes to the sandbox should take effect immediately. Changes to the production configuration are cached for up to 20 minutes, so be patient for them to take effect.

  • If you need help with testing regex itself, there are some external tools for this such as regex101.com (just make sure to test against the PCRE flavor, which is the default).
Performance tips
  • Try to keep the regex simple and short without allowing it to be too broad. For example, Huggle edits in English contain ([[WP:HG|HG]]) in the summary but the regex we use is \(\[\[WP:HG, since the piped part of the link isn't needed to safely conclude it is a Huggle edit.
  • Use tags wherever possible as they are significantly more efficient to query. Sometimes you have to include regex to account for edits made before the tag was introduced, in which case you should include both regex and the tag.
  • Restrict to applicable namespaces where possible, especially if the tool is not used in the mainspace or other popular namespaces.
Documentation

Please try to keep the definitions in the following order, with the entries sorted alphabetically:

  • Global list (nested the key "global")
    • List tools that are used extensively on multiple medium or large wikis. If only used on small wikis, it may be more efficient to list each of those individually for those wikis. Keep in mind any tools added under "global" are run for all wikis, and may unnecessarily slow down XTools on wikis that don't use those tools.
    • These tool definitions may include regular expressions, but should probably also include tags because the regex may not apply to non-English wikis.
    • You can also set wiki-specific regex that will get merged into the global regex (to override for each language, for example).
    • Other local values such as 'link', 'tag' and 'revert' are overridden, not merged into the global value.
    • See "Huggle" under "global" and "en.wikipedia.org" for an example.
  • Per-language list (such as "fr")
    • Key should match the ISO language code. All tools defined here will get ran for projects using that language.
    • These tool definitions generally only include native MediaWiki actions. For these, link to mediawiki.org documentation (e.g. mw:Special:MyLanguage/Help:Moving a page for the "Page move" tool).
    • The key should match the local name of the tool, and translations set using "label", along with the language-specific "regex" that goes with that tool.
  • Per-wiki list (such as "de.wikipedia.org")
    • Some definitions are only included to override values of global or per-language definitions.
Format for individual tool definitions

Either beneath "global", the language list (such as "fr") or under a wiki (such as "de.wikisource"), use any the following (only "regex" or "tag" are required):

  • Tool name (such as "Twinkle")
    • "regex" – Regular expression to match against edit summary. This follows PCRE format. Don't forget to escape regex literals using two backslash characters. For instance, to look for the link [[COM:FR|File renamed, you would use \\[\\[COM:FR\\|File renamed. Also shorten regex as much as possible. For example, the edit summary for "Undo" has changed over time – It could start with "undid", "undone" or "[[WP:UNDO|Undid]]", so our regex ends up looking like:
    ^(Undid|Undo|\\[\\[WP:UNDO\\|Undid\\]\\]) revision \\d+ by \\[\\[Special:(Contribs|Contributions)\\/.*?\\|.*?\\]\\]
    • "tags" – Names of tags applied to edits made using the tool, if applicable. See Special:Tags on the applicable wiki for full list.
    • "tag_excludes" – Don't count edits that also use this tag. This is used for example to hide Huggle edits when viewing Rollback edits. There are some known bugs, see phab:T191133. Please be careful using this option and test your changes thoroughly.
    • "link" – Wiki link to tool documentation. Full URLs or external links do NOT work, but interwiki do. Prefer official, multilingual documentation where possible (e.g. mw:Special:MyLanguage/Help:Moving a page instead of local documentation on moving pages). If no link exists, linking to the source code may be enough. If there's nowhere to link, it probably shouldn't be listed.
    • "label" – Text to use as the label for the tool, defaults to the tool's key. Use this for translations.
    • "revert" – If the tool is used only to revert edits (and not also issue talk page notifications, etc.), set this to true. If the tool is merely capable of reverting edits, set 'revert' to regex that would only account for such reverts. See the "Twinkle" entry for an example. The revert-only regex is necessary for the ArticleInfo and elsewhere in XTools, so as to differentiate edits that added content from edits that restored content.[1]
    • "contribs" – Set to true to include edits with the given tool in lists of non-automated contributions. For example, this is done for en.wikipedia's "ProveIt", because that tool often includes prose that was added by the user, and not entirely a semi-automated edit.
    • "namespaces" – The namespace IDs of where the tool is used. This is used to speed up the queries, so please use it where possible. Omit if the tool applies to all or most namespaces.
    • "talk_namespaces" – Set to only target talk namespaces.

For each tool definition, either "regex" or "tag" are required. In some cases you might want to include both, say if older versions of the tool did not add tags to the edits.

Responding to requests
  1. Ensure the tool meets the criteria outlined in the above guidelines.
  2. Test your changes first in the sandbox
  3. Make the changes to the production config.
  4. Mark the request as {{done}}


Notes

  1. ↑ However, XTools will eventually utilize the "reverted" tag to identify such edits, thus if the tool was introduced after September 2020 (after the "reverted" tag was introduced), it may not be necessary to set this option.
Request that a new (semi-)automated tool be added
SpBot archives all sections tagged with {{Section resolved|1=~~~~}} after 3 days and sections whose most recent comment is older than 365 days.

Ultraviolet

Latest comment: 2 months ago7 comments7 people in discussion
  • Wiki: en.wikipedia.org
  • Name of tool: Ultraviolet
  • Links to example edits: [1] [2] [3]
  • Link to the tool's documentation or homepage: Wikipedia:Ultraviolet

TheBigBookOfNaturalScience (talk) 03:20, 23 June 2023 (UTC)Reply

Support: per Wesoree TryAgainSooner (talk) 17:09, 9 September 2024 (UTC)Reply
A side note to participants: I think it's pretty clear already that UV should be on the list, given the volume of usage (174k); the reason it hasn't been done yet is I think more due to no one having gotten round to it than due to too low usage or lack of support. Volunteer time, &c...
TO whoever ends up doing this: do not add a regex; a tag should be largely sufficient, given that UW dates from 2022, and has always been tagged. — Alien  3
3 3 06:01, 2 June 2025 (UTC)Reply

Add afcrc-helper to English Wikipedia

Latest comment: 7 months ago3 comments2 people in discussion

I Am Andumé (talk) 02:40, 13 March 2024 (UTC)Reply

Support but exclusion to tag mw-new-redirect needs to be added, as the script is mainly used for creating cats and redirects. ~/Bunnypranav:<ping> 11:32, 11 December 2024 (UTC)Reply
To any admins that might be looking into this. Kindly keep it on hold till phab:T382773 is resolved. If added now, it will duplicate into the Redirect tool as well. Thanks! ~/Bunnypranav:<ping> 09:17, 29 December 2024 (UTC)Reply

Growth Team's "Add a link"

Latest comment: 10 months ago2 comments2 people in discussion

Unlike other Newcomer Tasks, these edits are machine suggested in a way that users just have to choose "Yes" or "No". Such semi-automated edits are tagged with newcomer task add link. Titore (talk) 19:05, 4 May 2024 (UTC)Reply

FTR, this has been done by Melos for the Italian Wikipedia. The issue with adding it everywhere is that it is not currently possible to add tools on a per-project basis translingually, i.e. there is no field like "all *.wikipedia.org projects"; while adding it into the "global" field would make it unnecessarily run on non-Wikipedia projects. cc @MusikAnimal. ~~~~
User:1234qwer1234qwer4 (talk) 14:20, 8 October 2024 (UTC)Reply

Add redirect-helper

Latest comment: 7 months ago3 comments2 people in discussion
  • Wiki: en.wiki
  • Name of tool: redirect-helper
  • Links to example edits: [8]
  • Link to the tool's documentation or homepage: [9]

~~~~ NW1223<Howl at me•My hunts> 02:22, 17 August 2024 (UTC)Reply

Support but exclusion to tag mw-new-redirect needs to be added, as the script is also used for creating redirects. ~/Bunnypranav:<ping> 11:33, 11 December 2024 (UTC)Reply
To any admins that might be looking into this. Kindly keep it on hold till phab:T382773 is resolved. If added now, it will duplicate into the Redirect tool as well. Thanks! ~/Bunnypranav:<ping> 09:17, 29 December 2024 (UTC)Reply

Update Genereric rollback and RedWarn

Latest comment: 8 months ago1 comment1 person in discussion

I propose that the RedWarn be updated from a regex query (present) and use the en.wiki tag RedWarn. See w:Special:Tags.

Also, the Generic rollback be updated to exclude tag RedWarn. This is in line with Generic rollback excluding huggle and twinkle.

Thanks! ~/Bunnypranav:<ping> 11:28, 11 December 2024 (UTC)Reply

IABotManagementConsole [1.3]

Latest comment: 13 days ago4 comments3 people in discussion

Ratnahastin (talk) 09:01, 29 December 2024 (UTC)Reply

  • Support
Nedia020415 (talk) 21:26, 8 February 2025 (UTC)Reply
  Done ~~~~
User:1234qwer1234qwer4 (talk) 02:56, 13 August 2025 (UTC)Reply
  This section is resolved and can be archived. If you disagree, replace this template with your comment. ~~~~
User:1234qwer1234qwer4 (talk) 02:57, 13 August 2025 (UTC)Reply

Reversão e Avisos

Latest comment: 7 months ago1 comment1 person in discussion

For instance, edits made using Reversão e Avisos get tagged with "diff-tools".

Cheers, Eduardo Gottert (talk) 02:00, 12 January 2025 (UTC)Reply

OpenRefine version 3.9

Latest comment: 13 days ago2 comments2 people in discussion

OpenRefine on PAWS is now updated to the version 3.9.0, and edits are currently not recognized by XTools as (semi-)automated. Is it possible to update the configuration, please?

  • Wiki: wikidata.org
  • Name of tool: OpenRefine
  • Links to example edits: [11]

PKalnai (talk) 15:22, 15 May 2025 (UTC)Reply

  Done ~~~~
User:1234qwer1234qwer4 (talk) 02:54, 13 August 2025 (UTC)Reply

Slash needs escaping

Latest comment: 2 months ago9 comments2 people in discussion

@1234qwer1234qwer4 (as the person who seems to be taking care of this): could you escape the slash in the regex for change status please? That is, "\[\[User:DannyS712/Change status\|Change status\.js\]\]" to "\[\[User:DannyS712\/Change status\|Change status\.js\]\]". Right now it still works in prod, but I think that's because prod's still on PHP 7.4. With newer versions of PHP it throws a "unknown modifier: C" exception, because we essentially slap slashes on it and match with that (not the best way, IK, but at least the regex we're feeding should be valid). — Alien  3
3 3 07:52, 1 June 2025 (UTC)Reply

@Alien333: There are a lot of slashes that are not escaped. – Phương Linh (T · C · CA · L · B) 07:54, 1 June 2025 (UTC)Reply
@Hide on Rosé: Most of them are in the links, not regexes, and so don't need to be escaped. I went through them all, and there's only one other regex with unescaped slash: "\\[\\[Usuario:Qwertyytrewqqwerty/DisamAssist\\|DisamAssist\\]\\]" → "\\[\\[Usuario:Qwertyytrewqqwerty\/DisamAssist\\|DisamAssist\\]\\]". — Alien  3
3 3 08:00, 1 June 2025 (UTC)Reply
I'm also pretty sure that's the cause of errors because:
  • on enws, the only wiki to have change status, we error on "C", the first letter
  • on enwp, that has neither of the two, everything works fine
  • on eswp, that has the second, we error on "a"; with D, i, s being valid regex flags in PHP (see [12]) — Alien  3
    3 3     08:04, 1 June 2025 (UTC)Reply
@Alien333: Should we use double-backslash instead of single one? – Phương Linh (T · C · CA · L · B) 08:03, 1 June 2025 (UTC)Reply
I don't think so: when a double backslash was used, it was because we wanted the regex result to contain an actual backslash character; here we merely want to prevent the / from being interpreted as a separator. — Alien  3
3 3 08:07, 1 June 2025 (UTC)Reply
@Hide on Rosé: after some more doubt and head-bonking: actually, you're right, we do want double slashes in the code. Had not wrapped my head around the fact that when displaying JSON MW shows the escaped version not the source. — Alien  3
3 3 20:05, 1 June 2025 (UTC)Reply

┌─────────────┘
 So in the end the changes to be done to the source are:

l. 1074: "regex": "\\[\\[User:DannyS712/Change status\\|Change status\\.js\\]\\]", to "regex": "\\[\\[User:DannyS712\\/Change status\\|Change status\\.js\\]\\]",

l. 1093: "regex": "\\[\\[Usuario:Qwertyytrewqqwerty/DisamAssist\\|DisamAssist\\]\\]", to "regex": "\\[\\[Usuario:Qwertyytrewqqwerty\\/DisamAssist\\|DisamAssist\\]\\]",

— Alien  3
3 3 20:12, 1 June 2025 (UTC)Reply

  Done Changes implemented. – Phương Linh (T · C · CA · L · B) 08:43, 2 June 2025 (UTC)Reply
Retrieved from "https://meta.wikimedia.org/w/index.php?title=MediaWiki_talk:XTools-AutoEdits.json&oldid=29119719"
Return to "XTools-AutoEdits.json" page.