Commons:History merging and splitting

From Wikimedia Commons, the free media repository
Jump to navigation Jump to search
Visualization of the merging process.

Shortcuts: COM:HMS • COM:HISTMERGE This page provides information on issues and solutions relating pages and files that underwent cut-and-paste moves (which its history has to be put back together), and inappropriate merging/overwriting (of which its history needs to be split).

History merging

Shortcut

Because most users have the ability to use the move page function, cut-and-paste moves are usually done by people who are not aware of that function, or when the move function fails (e.g. because the target has history), and people who aren't aware of the Administrators Noticeboard forum to ask for help from an administrator.

When a cut-and-paste move is done, the page history of a page can be split among two or more different pages. This is very undesirable, because we need to keep the history with the content for copyright reasons. In most circumstances, administrators are able to fix this by merging page histories.

Instructions for admins
  1. Temporarily delete NewPage
  2. Move OldPage to NewPage, using the move functionality. (In case it is a file, you have to open the Move & Replace link in a new tab or disable AjaxQuickDelete in your preferences.) (Now the old history versions are the whole of the new title’s.)
  3. Undelete the NewPage page, by:
    1. Viewing the page/file history
    2. Clicking “View or restore … deleted edits?”, and
    3. Clicking on “Restore!”. (Now the new title’s history has both the old and new versions, including an extra copy of the most recent version of OldPage, created by the move tool.)
  4. At this stage, NewPage will only show the text “#REDIRECT NewPage” (assuming a redirect was the most recent version of OldPage, the NewPage page will now be showing whatever the most recent version of OldPage was). The last step is to revert (or RevisionDelete) to the last version of NewPage from before the move.

Special:MergeHistory makes it possible to automatically merge the history of two pages.


History splitting

Over time, pages or files may change from one underlying topic to a completely separate topic. Normally, this should be accomplished through moves of pages, or by reuploading an altered file on a slightly different title. However, if a user is unfamiliar with those processes they may simply change the subject of a page or file (overwriting the old). If this is not caught immediately it is very easy for the new topic to build up a substantial edit history of its own.

Instructions for admins
  1. Temporarily delete the page/file (original title)
  2. Restore previous revisions up to (but not including) the point where the topic was changed.
  3. Move (without redirect) the restored versions (old topic) to the desired new title. (In case it is a file, you have to open the Move & Replace link in a new tab or disable AjaxQuickDelete in your preferences.)
    • If there’s already a file or page under the new title and you wish to histmerge into it:
    a) select the “delete the existing article” option, while moving;
    b) restore deleted revisions of new title.
  4. Restore new revisions of new topic (still at original title).

A history merge could also be undone in this way.

Requesting a merge or split

To request a merge or split, fill the following template, and submit it at the bottom of this page. Remember, both files need to be of the same type. Merging of more than two files may also be possible in some cases.

== [[:FILE/PAGE 1]] → [[:FILE/PAGE 2]] ==
* Request: [Split or Merge]
* Reason:
--~~~~
  • For merges, replace FILE/PAGE 2 with the page you want FILE/PAGE 1 contents to be merged into.
  • For splits, replace FILE/PAGE 2 with the new filename which you want the newer content to be moved from FILE/PAGE 1.
 

Current requests

View Edit Add topic

 See also categories: Media requiring a split up and Requested merges.
  • Request: Merge
  • Reason: The same file with same length

2001:871:25A:D13B:B9DB:B9C3:23C6:BF7A 08:22, 1 January 2025 (UTC)[reply]

✓ Done --Yann (talk) 11:04, 1 January 2025 (UTC)[reply]
Checkmark This section is resolved and can be archived. If you disagree, replace this template with your comment. --Sreejith K (talk) 15:24, 2 January 2025 (UTC)
  • Request: [Merge]
  • Reason: Both files are similar, so having them to merge as single file is necessary.

--Yayan550 (talk) 23:42, 1 January 2025 (UTC)[reply]

✓ Done --Sreejith K (talk) 15:23, 2 January 2025 (UTC)[reply]
Checkmark This section is resolved and can be archived. If you disagree, replace this template with your comment. --Sreejith K (talk) 15:23, 2 January 2025 (UTC)

--Colohisto (talk) 00:32, 3 January 2025 (UTC)[reply]

✓ Done --Sreejith K (talk) 14:52, 3 January 2025 (UTC)[reply]
Checkmark This section is resolved and can be archived. If you disagree, replace this template with your comment. --Sreejith K (talk) 14:52, 3 January 2025 (UTC)
  • Request: Merge
  • Reason: This film which is in the public domain originally had a synchronized soundtrack when released, the first file does not have not have the soundtrack, I uploaded the file with the soundtrack using video to commons but wasn't able to overwrite the first.

--Colohisto (talk) 00:30, 4 January 2025 (UTC)[reply]

  • Request: Merge
  • Reason: I was trying to overwrite File:Our Dancing Daughters (Harry Beaumont, 1928).webm by removing the metadata (there was a title in the metadata) but I wasn't able to upload it directly via the Commons upload wizard since the max file size for uploading from a computer is 100 MB. I had to use video2commons again to upload it to a new file.

--Colohisto (talk) 01:31, 4 January 2025 (UTC)[reply]

Request: Merge Reason: The same movie with different resolutions. 37.109.162.190 09:57, 6 January 2025 (UTC)[reply]

  • Request: Merge
  • Reason: It's the same movie.

OGPawlis (talk) 09:59, 6 January 2025 (UTC)[reply]

  • Request: [Merge]
  • Reason: Both files are essentially same image, so having two files combined together as single file (named File:Nickelodeon 2023 logo.png) is more necessary.

--2404:8000:1037:469:34A1:C55F:8C39:6D99 00:16, 11 January 2025 (UTC)[reply]

✓ Done --Sreejith K (talk) 04:41, 11 January 2025 (UTC)[reply]
Checkmark This section is resolved and can be archived. If you disagree, replace this template with your comment. --Sreejith K (talk) 04:41, 11 January 2025 (UTC)
  • Request: [Merge]
  • Reason: Both files show the same flag, they differ in details and the second one is correct. There is no need to duplicate this, nor to keep the old, inaccurate drawing.

--Swiãtopôłk (talk) 16:45, 13 January 2025 (UTC)[reply]

✓ Done --Sreejith K (talk) 20:26, 13 January 2025 (UTC)[reply]
Checkmark This section is resolved and can be archived. If you disagree, replace this template with your comment. --Sreejith K (talk) 20:26, 13 January 2025 (UTC)
  • Request: [Split]
  • Reason:The city has a new flag, but someone has overwritten the old file. Of course, it should be split, but it would be best if the new blue flag was the "Flag of Frankfort, Kentucky" file and the old white flag created a new file with the new name. This way, the graphics will be automatically replaced in all places.

--Swiãtopôłk (talk) 00:46, 14 January 2025 (UTC)[reply]

✓ Done --Sreejith K (talk) 22:34, 14 January 2025 (UTC)[reply]
Checkmark This section is resolved and can be archived. If you disagree, replace this template with your comment. --Sreejith K (talk) 22:34, 14 January 2025 (UTC)
  • Request: Merge
  • Reason: Someone uploaded version of the same film with higher resolution. Please merge both files under name "The Mark of Zorro (1920)".

5.184.250.125 20:19, 14 January 2025 (UTC)[reply]

  • Request: [Merge]
  • Reason: duplicate file, same size

--Kiran891 (talk) 02:14, 15 January 2025 (UTC)[reply]

✓ Done Merged the files using {{Duplicate}} tag. --Sreejith K (talk) 13:32, 15 January 2025 (UTC)[reply]
Checkmark This section is resolved and can be archived. If you disagree, replace this template with your comment. --Sreejith K (talk) 13:32, 15 January 2025 (UTC)

See also