Wikipedia:Bots/Requests for approval/Aidan9382-Bot 2

The following discussion is an archived debate. Please do not modify it. To request review of this BRFA, please start a new section at Wikipedia:Bots/Noticeboard. The result of the discussion was  Approved.

Aidan9382-Bot 2

New to bots on Wikipedia? Read these primers!

• Approval process – How this discussion works
• Overview/Policy – What bots are/What they can (or can't) do
• Dictionary – Explains bot-related jargon

• (BRFA
• Approved BRFAs
• talk
• contribs
• count
• SUL
• logs
• page moves
• block log
• rights log
• flag)

Operator: Aidan9382 (talk · contribs · SUL · edit count · logs · page moves · block log · rights log · ANI search)

Time filed: 17:31, Wednesday, June 8, 2022 (UTC)

Function overview: Fix the |archive= location for the {{User:MiszaBot/config}} template which is used by Lowercase Sigmabot III for archiving.

Automatic, Supervised, or Manual: Automatic

Programming language(s): Python

Source code available: GitHub

Links to relevant discussions (where appropriate):

Edit period(s): Continuous (Every 15 minutes or so)

Estimated number of pages affected: Few initially, as I have been manually clearing the category for some time. Around 0 to 5 per day on average.

Namespace(s): All talk namespaces, as these are where archiving takes place

Exclusion compliant (Yes/No): Yes

Function details: This bot is designed to automatically fix any wrong inputs put into the |archive= parameter of {{User:MiszaBot/config}}, which Lowercase Sigmabot III relies on for archiving talk pages. These archives normally become incorrect after a page move which an editor has forgotten to clear up. Broken articles are findable via the associated category.

Discussion

 Note: While this is listed as task number 2, the previous task was actually withdrawn by operator. I'm assuming the correct move here is to just consider this the second task, but please correct me if I'm wrong. Thanks. Aidan9382 _(talk) 17:31, 8 June 2022 (UTC)

@Aidan9382: This is the correct numbering for a bot task. What do you think an appropriate number of edits would be for a trial run? The standard is 50, but can be modified and seems a bit high for this unless I'm mistaken. --TheSandDoctor ^Talk 15:54, 19 June 2022 (UTC)

@TheSandDoctor: I'd say its high for this, as this case doesnt happen too often. If you want a lower count, maybe 20 or 25? I'm concerned any lower might be too low to cover any potential weird cases. Aidan9382 _(talk) 15:58, 19 June 2022 (UTC)

• @Aidan9382: You've got it. Approved for trial (25 edits). Please provide a link to the relevant contributions and/or diffs when the trial is complete. --TheSandDoctor ^Talk 16:01, 19 June 2022 (UTC)

@TheSandDoctor: Trial complete. The 25 are here (excluding 3 development edits). Other than an issue with encoding (Special:Diff/1094354270) and another with my template parsing (Seen testing here) which have both since been fixed, the edits have worked as intended. Aidan9382 _(talk) 15:32, 27 June 2022 (UTC)

---

 Approved. Under normal circumstances, I would prefer to leave the close for someone else. However, given the backlog, lack of recent BAG activity (myself included), and the fact that this task is uncontroversial and based on how well the trial went, I am inclined to make an exception for this. As per usual, if amendments to - or clarifications regarding - this approval are needed, please start a discussion on the talk page and ping. Please be sure to monitor this task and address any further edge cases that arise. --TheSandDoctor ^Talk 18:23, 9 July 2022 (UTC)

The above discussion is preserved as an archive of the debate. Please do not modify it. To request review of this BRFA, please start a new section at Wikipedia:Bots/Noticeboard.

Expanding on the task

@TheSandDoctor (or others): After a notice from another editor about a month back or so about the bot potentially causing issues (See here), I had significantly cut-down on the "confidence" of the bot, as to avoid it from changing the parameter if it wasn't sure 100% the archives had been correctly moved, and had it alert me for anything concerning. Over the past few days, I've been looking into improving on how much I had cut it down, and recently finished. The main idea is that, now, the bot will try to locate which page it was moved from and to move any /Archive subpages under it to the new location (given the move was uncontested for ~4h as to not start a subpage move war) (new code will be uploaded to the github for reference Soon^TM has been uploaded).

The whole reason I'm posting it here is because I'm not sure if this is considered a reasonable extension of the current task, or if I should start up more of a discussion beforehand. I've done testing here/here to confirm it works, but I don't want to just immediately roll it out without making sure.

It might just be me being over-careful like I've done before, but I thought I'd ask anyways. Thanks. Aidan9382 _(talk) 14:05, 14 November 2022 (UTC)

Thanks for the notice, @Aidan9382:. You can consider this approved. TheSandDoctor ^Talk 21:15, 14 November 2022 (UTC)