Wikipedia talk:Merging

  1. Home
  2. Wiki

Merging Drafts

[edit]

How should I go about merging a draft with an existing article? The draft does not belong to me. Editor113u47132 (talk) 21:52, 10 April 2025 (UTC)[reply]

I assume you just copy material from the draft to the article just like a regular merge. Indicate where the material came from in an edit summary or with {{merged-from}}. There is an interesting question about attribution as it is likely the draft will eventually be deleted. ~Kvng (talk) 14:29, 26 April 2025 (UTC)[reply]
[edit]

recent AfD was closed as redirect Wikipedia:Articles for deletion/Ali Khamis Rashid Al-Neyadi. An editor has tried to merge (not redirect) content as in this edit. I'm asking the community if this is an appropriate action. LibStar (talk) 17:29, 11 April 2025 (UTC)[reply]

I think you can treat that as a normal content dispute. The community has decided that this subject is not notable enough to merit a stand-alone article. Whether they're notable enough for mention in another article is something for editors of the other article to decide separately. ~Kvng (talk) 14:35, 26 April 2025 (UTC)[reply]

Image replacement

[edit]

Anyone interested in replacing File:ESA Patch 2022.png as an example of a non-free logo in Wikipedia:Merging#How to merge? Thanks, it's lio! | talk | work 14:40, 18 April 2025 (UTC)[reply]

You can pick something from Category:Non-free logos. 174.138.212.166 (talk) 21:14, 9 July 2025 (UTC)[reply]

Merging draft with mainspace

[edit]

I merged Draft:Grand Chess Tour 2025 with the mainspace article which was created before the draft could be moved to mainspace. I linked the original draft in my edit summary, but since drafts eventually get deleted, the edit history and attribution would get lost. A similar issue was also raised in an above section. Any solution? 9ninety (talk) 13:55, 3 May 2025 (UTC)[reply]

Just use {{R with history}}. 174.138.212.166 (talk) 21:10, 9 July 2025 (UTC)[reply]

Procedural closure due to an AFD?

[edit]

Hi all. There's a bit of an odd situation at placeholder name. The article is now at Wikipedia:Articles for deletion/Placeholder name. Prior to the AFD nom two separate merge proposals were made to merge many different articles to placeholder name. The article however may not exist for much longer depending on the outcome of the AFD. Should we allow both processes to continue or should the merge proposals be tabled for now and closed pending the outcome of the AFD? Best.4meter4 (talk) 04:18, 9 August 2025 (UTC)[reply]

There is currently consensus not to use placeholder name as the destination for the "English placeholder names for people" articles, and the other merge proposal has received nothing but opposition and a different target has also been suggested.
Even if placeholder name is kept as-is, it seems no articles will be merged into it. FaviFake (talk) 09:42, 9 August 2025 (UTC)[reply]
Yes, but the consensus is to merge in the other discussion involving John Doe, et al. That’s a problem.4meter4 (talk) 10:25, 9 August 2025 (UTC)[reply]
Hmmm... In reading it again, perhaps you are correct that the consensus is towards a different target article.4meter4 (talk) 10:32, 9 August 2025 (UTC)[reply]
Yes, merges, renaming and other potentially discussion destabilizing activities should be put on hold while an AfD progresses, see WP:EDITATAFD. ~Kvng (talk) 16:12, 9 August 2025 (UTC)[reply]

RFC needed on moving open WP:MERGEPROP discussions to different talk pages

[edit]

Based on what is currently happening at Talk:Placeholder name#Proposed merger of Oceanic Airlines into Placeholder name and its subsequent move to Talk:Fictional company#Proposed merger I think we need to have a serious discussion about procedural process for when a new target article is proposed for a merge. When it became clear that the original proposal to merge Oceanic Airlines to Placeholder name was clearly failing, the solution by FaviFake, the nominator, was to change the proposal to a new target article Fictional company which had cropped up as a suggested new place to merge. At that point the Placeholder name article was no longer pertinent to the merge discussion and yet the conversation was happening at Talk:Placeholder name. I argued that we should close it down for this reason and start a new WP:MERGEPROP be made so that a discussion could happen on a relevant talk page of one of the article's involved in the merge which procedurally I think is the least disruptive. Faviflake overruled this and then proceeded to copy paste the discussion (without discussion) at Talk:Fictional company#Proposed merger. This then ended up being discussed at Wikipedia:Administrators' noticeboard/Incidents#Clarity needed on moving talk page discussions during merge prop where an admin pointed out serious procedural problems with this move by interference with bots and their automated processes at MERGEPROP.

The problem I see with that is not only does it interfere with the bot processes in notifications/other technical stuff but it makes archiving very difficult by spreading a conversation across multiple talk pages. To me it's extremely disruptive at WP:MERGEPROP and I don't think we should allow talk page moves at all during a MERGEPROP. I would propose a simple solution to this which would be that we require the MERGEPROP discussions to occur on the page that is being merged into a target article and not on the target article page. That way if a new target article is proposed the conversation can continue without it being disruptive to the bot process or requiring a page move. Additionally I think we need to make it clear that if for some reason it is better to move to a new talk page that the discussion must be closed and a new MERGEPROP made at that page (ie a fresh start). This would bring better clarity to our process and prevent future issues of this kind. Thoughts?4meter4 (talk) 17:16, 11 August 2025 (UTC)[reply]

Hey there, it's always nice being mentioned in your posts. I'd like to give some context about the situation:

I argued that we should close it down for this reason [...]

Before you argued, you closed the discussion as an involved editor. It seems you did this because you misinterpreted my message, but I just thought it'd be relevant and should be mentioned.

This then ended up being discussed at [ANI] [...] where an admin pointed out serious procedural problems [...]

To be clear, the ANI thread was created by you and the only question the admin asked is "can we be certain that the bots and scripts will update the pages that point to the original location?"
As I explained at length here, I have fixed the bot issues and updated every page where the merger target for Oceanic Airlines was Placeholder name to "Fictional company". As you can see on this search, there are no more incorrect notifications about this merger. I explained to you that this should satify any concerns RedRose had about my edits.
They never mentioned "serious procedural problems"; they only said my actions were improper because I didn't update the notifications sent out by bots, and that issue is now fully resolved.

it makes archiving very difficult by spreading a conversation across multiple talk pages

I don't see how this kind of moves would cause archiving bots to break. The move notices are all correctly timestamped and they will be archived as usual. This practice is normal; for example at Wikipedia talk:Deletion process § "Wikipedia:DPROCESS" listed at RfD, a discussion was moved elsewhere with this diff by the OP because they thought it wasn't relevant in the OG talk page anymore.
And the conversation isn't "spread across pages", it's all in one place with at Talk:Fictional company § Proposed merger. Following the example above, I have removed the duplicate discussion over at Talk:Placeholder name § Proposed merger of Oceanic Airlines into Placeholder name, leaving a link to the correct section.
I only chose to move the discussion because the majority of editors in the discussion said they believed Fictional companies to be a better target for the merger, and because 4meter4 attempted to close it for this reason. Consensus was forming to merge the page into Fictional companies instead of the original target, so I moved it to allow it to continue and to satisfy the concerns of improper notification and labelling of the different pages.
Editors' time is a valuable resource that I didn't want to waste by disregarding the previous discussion and starting from scratch. I haven't been made aware of any policies advising against the practice and I don't think the change you're suggesting should be applied (for many reasons, which I'm sure are listed elsewhere); I'm mainly corcerned that it will result in less editors partecipating in merge discussions because of the lower visibility of the souce page copared to the destination page, and I don't think the risk of the target page changing is enough to warrant a policy change. Additionally, I think moving merge discussions should be encouraged or at least allowed, to avoid wasting people's time and get clearer consensus. FaviFake (talk) 18:00, 11 August 2025 (UTC)[reply]
You've mischaracterized what was said at ANI. Redrose64 stated I would say that FaviFake has performed a series of improper actions. Your actions were improper which is why an RFC is necessary.4meter4 (talk) 02:35, 14 August 2025 (UTC)[reply]
You have too. An admin didn't "[point] out serious procedural problems."
I agree an RfC is needed if you want to change the policy. But I suspect our two walls of text and this backstory would not get much interest. You could ask, "Should this sentence in [policy name] be added/changed? "Merge and split discussions should only be held at the source page, not the destination of the merge or split."
Your original argument was "[...] other editor's comments get copy pasted to a different talk page without their consent. I'm not ok with this", while now it has shifted to "it interfere[s] with the bot processes in notifications/other technical stuff [and] it makes archiving very difficult". As I explained, I don't personally believe these to be good enough reasons for such a drastic change, since the first one is a standard process and the second one is easily fixable. But feel free to go ahead if you believe otherwise. FaviFake (talk) 10:37, 14 August 2025 (UTC)[reply]
I haven’t done anything procedural in this case, so there is no “you have too”. Further improper actions means improper procedural behavior in this context. Please refrain from wall of text responses that are frankly inaccurate representations of reality. This is becoming WP:DISRUPTIVE.4meter4 (talk) 14:10, 14 August 2025 (UTC)[reply]
You seem to have misread my message; I said "You have too", not that "you have to" do it. FaviFake (talk) 14:14, 14 August 2025 (UTC)[reply]
It was a typo. I didn’t misread it.4meter4 (talk) 14:22, 14 August 2025 (UTC)[reply]
Oh, then my reply wasn't clear. I meant you've mischaracterized what was said at ANI too. FaviFake (talk) 14:25, 14 August 2025 (UTC)[reply]
No I haven’t. You don’t understand what was said at ANI, and continue to not understand.4meter4 (talk) 14:39, 14 August 2025 (UTC)[reply]
This conversation has been very productive so far; I suggest we continue bickering until the issue resolves itself. FaviFake (talk) 14:44, 14 August 2025 (UTC)[reply]
The whole point of this conversation was to follow RFC pre-procedure as required to do before instigating an RFC. That requires outside community engagement and a period of public comment.4meter4 (talk) 15:11, 14 August 2025 (UTC)[reply]
Yes, I know. To attract more editors, you could consider notifying Wikipedia:WikiProject Merge and Wikipedia:Help Project. FaviFake (talk) 16:02, 14 August 2025 (UTC)[reply]

Not sure if I merged correctly? Help, please.

[edit]

Earlier this year, an editor created the Godzilla (Showa); it basically serves as an all-encompassing character article for the 15 iterations of Godzilla from the franchise's Showa period (1954—1975). But a week ago, the same editor created a separate character article for the first incarnation from 1954 [1]. I brought up on the talk page that a separate article for the '54 variant doesn't make sense when it can be covered in the Godzilla (Showa) article [2]. The OP realized their mistake and seemingly agreed to my proposal to merge the articles [3]. I tried to merge it myself but I'm not sure if I did it right? Please help.

Also, forgive me if I crossed some lines in my attempts to merge. This was my first time doing anything like this. I tried to follow WP:PROMERGE as best I could. Armegon (talk) 05:33, 16 August 2025 (UTC)[reply]

Thanks for both proposing the merge and acting on it! You've got the talk page templates and the redirect right; the one main thing I can't see are clear edit summaries on Godzilla (Showa) to indicate which of the many edit you performed on the 16th August relate to merge and which don't. It's better to do a 'full content merge', merging with one edit as much of the content as you intend to move, marking in the edit summary Merged content from [[source page]] to here. See [[Talk:merge discussion section]]. You can then tidy it up with further edits. So, you might want to read point 1 in WP:PROMERGE again. It's also helpful, even if you don't formally closed the discussion (not really necessary for very short discussions), to add at the end of the discussion something like template:merge done, which marks to readers of the talk page that this has been completed (rather than them starting to think about the discussion - they might not think to look at the template at the top of the page). There also seems to have been some confusion on the talk page regarding a move and a merge, but a solution seems to have been found; I haven't reviewed the completeness of the merge of the referenced content (tricky to to with that edit history). Klbrain (talk) 11:25, 16 August 2025 (UTC)[reply]
Thank you so much! Armegon (talk) 16:33, 16 August 2025 (UTC)[reply]