Wikipedia talk:Requested moves

This is the talk page for discussing Requested moves and anything related to its purposes and tasks.

Add new text under old text.
New to Wikipedia? Welcome! Learn to edit; get help.

Start a new topic

WT:RMWT:RM

NOTE: This is not the place to request moves. Please follow the instructions given on the project page. If you seek instruction on closing existing requests, please see the closing instructions.

To help centralize discussions and keep related topics together, most subpages of Wikipedia:Requested moves that are unused have talk pages that redirect here.

This page has previously been nominated to be moved. Please review the prior discussions if you are considering re-nomination.

Discussions

RM, WP:Requested moves → WP:Proposed moves, No consensus, 7 June 2007
RM, WP:Requested moves → WP:Proposed moves, Not moved, 11 February 2018
RM, WP:Requested moves → WP:Articles for renaming, Not moved, 19 September 2018
RM, WP:Requested moves → WP:Requested title changes, Not moved, 22 July 2024

Enter the title (or part of a title) to search for after "intitle:", then click "search"

Try other variants (e.g. "move discussion") to broaden or narrow your search

Archives

Index 1, 2, 3, 4, 5, 6, 7, 8, 9, 10
11, 12, 13, 14, 15, 16, 17, 18, 19, 20
21, 22, 23, 24, 25, 26, 27, 28, 29, 30
31, 32, 33, 34, 35, 36, 37

Administrators' noticeboard/Move requests (2005)
For why RM was created, see:
- requested moves -- policy change?

Archives by date

This page has archives. Topics inactive for 30 days are automatically archived by if there are more than 5.

RM/TR section heading changes

See User talk:Eejit43#RMTR helper. This may or may not brick scripts and bots as a breaking change. Posting here for wider visibility as we're not entirely sure what would be affected, and whether it should be done. So far, what needs to be changed would be my bot and RMTR helper. Ideally the switch should be planned so there's no downtime. Also pinging Eejit43 and FaviFake of this discussion. — Tenshi! (Talk page) 15:28, 7 May 2026 (UTC)[reply]

Wikipedia talk:Twinkle/Archive 49#RM/TR generator failed to find target section notes that Twinkle would also need to be changed. Rotideypoc41352 (talk · contribs) 18:45, 8 May 2026 (UTC)[reply]

This seems to be a recurring issue. If the templates keep being used incorrectly, people will keep fixing them to follow our guidelines. FaviFake (talk) 19:34, 8 May 2026 (UTC)[reply]

I left a note over at WT:TW pointing to here. Tenshi! (Talk page) 23:09, 8 May 2026 (UTC)[reply]

Looking at Twinkle's code, looks like it looks for ==== Requests to revert undiscussed moves ====, then adds the new RM/TR above it. So in short, any change to the wikicode ==== Requests to revert undiscussed moves ==== will break Twinkle's RM/TR feature unless it is patched first. Are you proposing changing that to something else? If so what will the new code be? –Novem Linguae (talk) 06:12, 9 May 2026 (UTC)[reply]

The changes proposed by FaviFake to section headings is Special:Diff/1352662973, assumedly to all of the section headings. Tenshi! (Talk page) 10:10, 9 May 2026 (UTC)[reply]

Not sure what specific change you're proposing, but would it be possible to program the scripts and bots to look for two alternative headers, so that the switch can be seamless? Toadspike [Talk] 07:47, 9 May 2026 (UTC)[reply]

I assume you mean to look for the current headers and the new headers, that's likely doable. Tenshi! (Talk page) 10:10, 9 May 2026 (UTC)[reply]

Wouldn't this approach be as fragile as the current one, though? As soon a a guideline changes, or if anyone wants to add an additional anchor or edit the current one (for whatever reason), all these scripts will have to be updated again.

Would it be technically feasible to check if a line contains two pairs of ==== and then check if a specific string (for example Requests to revert undiscussed moves) appears inside the pair of ====s? This would also allow us to change the heading displayed to readers without having to update the scripts. For example, this string would still work:

====<span class="anchor" id="Requests to revert undiscussed moves"></span>Requests to undo undiscussed moves==== FaviFake (talk) 11:02, 9 May 2026 (UTC)[reply]

@Tenshi Hinanawi, yes, exactly. @FaviFake, yes, it would still be fragile, but at least for this one transition it'll work with no downtime. I understood Tenshi's earlier idea as trying to coordinate updates to rmtrhelper, Twinkle, and the bot to happen at the same time, which would presumably have some downtime. I agree that a more sustainable solution using hidden anchors or something else would be a good idea. Toadspike [Talk] 11:04, 9 May 2026 (UTC)[reply]

Adding [^\n]+ ? to the RegEx should make Twinkle compatible with both. RegEx101. Should I go ahead and make that change? –Novem Linguae (talk) 15:05, 9 May 2026 (UTC)[reply]

Sure! FaviFake (talk) 16:13, 9 May 2026 (UTC)[reply]

Tracked in github.com
Issue #2361

Wrote the patch at [1]. –Novem Linguae (talk) 12:00, 10 May 2026 (UTC)[reply]

To be clear, my patch is in code review and is not deployed yet. Feel free to ping me if all other scripts get updated and you are just waiting on twinkle, and I will expedite it. –Novem Linguae (talk) 06:25, 11 May 2026 (UTC)[reply]

Twinkle's done now. All updated. –Novem Linguae (talk) 06:34, 16 May 2026 (UTC)[reply]

I have added support for this, using similar regex to what Novem is adding to Twinkle. You can see it in this git commit, and the update to the script code in this diff (minified, don't even bother reading...). All good on my end now, it will respect any content before the header name so if further shortcuts are added later down the line, support will not need to be added. ~ Eejit43 (talk) 03:39, 11 May 2026 (UTC)[reply]

FYI the other script I was thinking of that could be affected was TheTVExpert's submitRMTR script, but the logic there would not be affected by this change. ~ Eejit43 (talk) 03:42, 11 May 2026 (UTC)[reply]

I looked at their other script, User:TheTVExpert/rmCloser.js, and I'm pretty sure that this would break it as it checks for the RMUM header. It would also affect Move+ which derives from that script. Pinging BilledMammal. Tenshi! (Talk page) 21:21, 11 May 2026 (UTC)[reply]

True, rmCloser and Move+ will definitely be affected by this. We'll possibly need an interface admin to fix the former as @TheTVExpert has not edited in the last 2 years, and the script is still utilized by a large amount of editors. ~ Eejit43 (talk) 22:54, 11 May 2026 (UTC)[reply]

If someone wants to write and test a patch, you can use {{IAER}} on the talk page of the user script to summon an interface admin to implement the change. –Novem Linguae (talk) 03:21, 12 May 2026 (UTC)[reply]

(four days later) Hopefully, the request I've put in at User talk:TheTVExpert/rmCloser#Edit request 16 May 2026 is right. Rotideypoc41352 (talk · contribs) 06:17, 16 May 2026 (UTC)[reply]

rmCloser updated! Rotideypoc41352 (talk · contribs) 21:13, 18 May 2026 (UTC)[reply]

Done Move+ BilledMammal (talk) 00:43, 13 May 2026 (UTC)[reply]

(Special:Diff/1353888086 for future readers' easy reference.) Rotideypoc41352 (talk · contribs) 02:05, 14 May 2026 (UTC)[reply]

Greetings, Tenshi! Is TenshiBot ready? Rotideypoc41352 (talk · contribs) 21:13, 18 May 2026 (UTC)[reply]

I haven't had time to rewrite the code that it relies on to find the section headers yet. It could probably be switched over and it'd be fine as long as the search strings are updated, but it wouldn't be future-proofed for any other changes. Tenshi! (Talk page) 00:09, 20 May 2026 (UTC)[reply]

In the user scripts and gadgets above, we've just been adding regex wildcards. You might want to look into that solution. That might be both easy and future proof. –Novem Linguae (talk) 00:27, 20 May 2026 (UTC)[reply]

I'm aware of that, it's more that I have to replace .index() with regex, or alternatively rewrite the rest of the code to handle requests without breaking up lines. Tenshi! (Talk page) 15:34, 20 May 2026 (UTC)[reply]

Sorry to necro the thread three weeks later; for future readers who would like to know what happened: back on 20 May 2026, I changed the headings and remove all requests link, and Tenshi implemented a fix for TenshiBot (git commit). Rotideypoc41352 (talk · contribs) 19:51, 12 June 2026 (UTC)[reply]

It can and will freak out if any change is made to the headings, unfortunately. I'll try to work on this now that I've been reminded to write a better solution. Tenshi! (Talk page) 20:00, 12 June 2026 (UTC)[reply]

Done. Tenshi! (Talk page) 20:51, 12 June 2026 (UTC)[reply]

And the new solution works (Special:Diff/1359148121)! Rotideypoc41352 (talk · contribs) 21:10, 13 June 2026 (UTC)[reply]

RM as a way to nominate an article for deletion

Wikipedia:Deletion process#Deletion discussion venues currently lists Wikipedia:Requested moves as one of the places where editors can "formally" "nominate" an article for deletion (not merely as a technical matter). Please see Wikipedia talk:Deletion process#Moving a page as a deletion process. WhatamIdoing (talk) 18:13, 25 May 2026 (UTC)[reply]

Bot/bot, Feedback Needed RM/TR maintenance bot

Hello folks, I am developing a bot, see User:ThilioBot, which is intended to assist editors with TR and RM requested move discussions. The bot's purpose is only to work in the RM/TR space and monitor the RM space. It can detect possible duplicate RM/TR requests by searching the history, and when it finds a match it will comment under the request with a diff of the previous request. Also, when an editor submits a move request in RM/TR after or while the request already has an active RM discussion, the bot will automatically comment under the request that there is an active RM discussion, with a diff of that discussion. see

Its work is only to post informational maintenance comments to help editors identify previous or ongoing discussions. Feel free to say or ask anything about this, whether good or bad. SAWA!! CONFUSED SPIRIT(Thilio).Talk 09:29, 27 May 2026 (UTC)[reply]

Is there a want for this by RM/TR regulars? Also do you have any code published yet? Tenshi! (Talk page) 10:32, 27 May 2026 (UTC)[reply]

First time posting this here (gathering info) to see whether this would actually be useful or not especially regarding dup requests and active RM discus/on, as for the code I currently have working test version running on Toolforge and testing in User:ThilioBot/RMTRTest. CONFUSED SPIRIT(Thilio).Talk 10:51, 27 May 2026 (UTC)[reply]

Any suggestions? CONFUSED SPIRIT(Thilio).Talk 10:52, 27 May 2026 (UTC)[reply]

Could you create a user page for the bot? Tenshi! (Talk page) 15:16, 27 May 2026 (UTC)[reply]

Done. Trying to redirect the talk page but it refused CONFUSED SPIRIT(Thilio).Talk 18:37, 27 May 2026 (UTC)[reply]

It should use *: for replies per WP:LISTGAP. Tenshi! (Talk page) 15:23, 28 May 2026 (UTC)[reply]

Alright lemme add... CONFUSED SPIRIT(Thilio).Talk 15:31, 28 May 2026 (UTC)[reply]

Done CONFUSED SPIRIT(Thilio).Talk 15:36, 28 May 2026 (UTC)[reply]

[Here updated] CONFUSED SPIRIT(Thilio).Talk 16:07, 28 May 2026 (UTC)[reply]

That sounds like a great idea. I've seen at least a couple of cases where contested technical requests are removed as stale and then reappear later as fresh TRs. Station1 (talk) 19:38, 27 May 2026 (UTC)[reply]

That's exactly what the bot is going to do search the RM/TR history for old requests and if it finds one, it will comment under the new request with a diff linking to the old request. What do you think about the comment wording? Open for suggestions

1. active redirect move discus/on...

Automated comment: There is currently an active requested move discussion involving x → z (diff).

2. dup (reappear as fresh) TRs...

Automated comment: A previous request involving Z → W appears to have been made before (diff). CONFUSED SPIRIT(Thilio).Talk 00:13, 28 May 2026 (UTC)[reply]

Could you make it so that it also pings the requester? HurricaneZeta^C 00:30, 28 May 2026 (UTC)[reply]

Oh, thank you @HurricaneZeta, that slipped my mind, will implement it. it's actually one of the important gags CONFUSED SPIRIT(Thilio).Talk 00:36, 28 May 2026 (UTC)[reply]

Successfully

Done. now it can pings the requester diff CONFUSED SPIRIT(Thilio).Talk 06:29, 28 May 2026 (UTC)[reply]

Discussion at Wikipedia talk:Attempting to overturn recent consensus#Moratoria

There is a discussion at Wikipedia talk:Attempting to overturn recent consensus#Moratoria that might be of interesting to readers of this page. Katzrockso (talk) 16:31, 27 May 2026 (UTC)[reply]

How do I change a single page move to a multi-page move?

So mid-discussion at Talk:Kawan, Kawan (disambiguation) was created. How do I go about updating the suggestion to the move? TansoShoshen (talk) 17:01, 27 May 2026 (UTC)[reply]

I need help in moving a page

Today I was talking to my good friend Joe Sanchez the former NYPD officer. He knows the other Joe Sanchez, a politician who also has an article here. People are getting confused when looking then up.Therefore Joe Sanchez Has requested that his article be renamed. He would like it to be named "Joe Sanchez (NYPD)". Thank you. ~2026-34200-18 (talk) 06:23, 11 June 2026 (UTC)[reply]

I've added a hatnote pointing to the Joseph Sanchez disambiguation page. That should take care of any confusion. Station1 (talk) 18:08, 12 June 2026 (UTC)[reply]

Jurong FC

https://en.wikipedia.org/wiki/Albirex_Niigata_Singapore_FC most parts of the article already renamed Эльдар Шукоров (talk) 11:03, 12 June 2026 (UTC)[reply]

Reverted apparent vandalism

See https://en.wikipedia.org/w/index.php?title=Wikipedia%3ARequested_moves%2FClosing_instructions&diff=1360671545&oldid=1360386194 . --User:Ceyockey (talk to me) 23:16, 22 June 2026 (UTC)[reply]

Thanks, though for future reference simple vandalism reverting doesn't need to be reported here. Primefac (talk) 11:15, 23 June 2026 (UTC)[reply]

Relevant proposal about renaming the move function to rename

In case anyone here doesn't know about it, see Wikipedia:Village pump (proposals) § Rename "move" to "rename". Graham87 (talk) 15:02, 23 June 2026 (UTC)[reply]

Proposal for early closes

Can we add to Wikipedia:Requested_moves/Closing_instructions#Early_closure these two other circumstances in which an early close may be performed?

Technical restrictions: The proposed title is not practicable due to technical restrictions.
Wrong venue: The requested move does not propose changing a title, but rather to delete, merge, split, or BLAR an existing article.

―Howard • 🌽³³ 00:49, 24 June 2026 (UTC)[reply]