Movatterモバイル変換

[0]ホーム
URL:

Jump to content
WikipediaThe Free Encyclopedia
Search

Wikipedia:Merging

Page semi-protected
From Wikipedia, the free encyclopedia

Wikipedia information page
"WP:MERGE" and "WP:DA" redirect here. For the WikiProject, seeWikipedia:WikiProject Merge. For merging of page histories, seeWikipedia:History merging. For articles with duplicated content, seeWikipedia:Content forks. For the list of oldest unedited articles, seeWikipedia:Database reports/Forgotten articles.
Wikipedia information page
This is aninformation page.
It is not anencyclopedic article, nor one ofWikipedia's policies or guidelines; rather, its purpose is to explain certain aspects of Wikipedia's norms, customs, technicalities, or practices. It may reflect differing levels ofconsensus andvetting.

Amerge ormerger is the process of uniting two or more pages into a single page. It is done by copying some or all content from the source page(s) into the destination page and then replacing the source page with aredirect to the destination page.

Any editor can perform a merge. No permission or discussion is needed if you think the merge is uncontroversial;just do it (but it might get reverted). Otherwise, the merge should be first proposed and discussed, as detailed below.

When performing a merge, one should remember to reconcile talk pages, and to attribute copied content, asrequired by Wikipedia's license. At minimum, this means adding words "Merged content to/from [[page]]" toedit summaries.SeeHow to merge below for details.

Reasons for merging

Shortcuts
"WP:DUPLICATE" redirects here. For other, seeWikipedia:Duplicate (disambiguation).

There are several good reasons to merge pages:

  1. Duplicate: There are two or more pages on exactly the same subject, with the same scope. If a duplicate article was recently created, it may also be a candidate for speedy deletion underCSD A10 criteria.
  2. Overlap: There are two or more pages on related subjects that have a large overlap and might beWP:REDUNDANT. Remember,Wikipedia is not a dictionary; there does not need to be a separate entry for every concept. For example, "flammable" and "non-flammable" can both be explained in an article onflammability.
  3. Short text: If a page is very short (consisting of perhaps only one or two sentences) and is, in your opinion as editor, unlikely to be expanded within a "reasonable" (unspecified) amount of time, it often makes sense to merge it into a page on a broader topic.
  4. Insufficient notability: Some topics may not reach thegeneral notability guidelines, or more specific criteria, so merging is analternative to deletion. While this can also be implemented through thearticles for deletion process, merging directly may be more efficient. For example, parents or children of a celebritywho themselves are otherwise unremarkable are generally covered in a section of the article on the celebrity.
  5. Context: If a short article requires the background material or context from a broader article in order for readers to understand it. For example, minor characters from works of fiction are generally covered in a "List of characters in <work>" article (and can be merged there); see alsoWikipedia:Notability (fiction).

Shortcuts

Merging should be avoided if:

  1. The resulting article would betoo long or "clunky", or
  2. The separate topics could be expanded into longer standalone (but cross-linked) articles

Procedure

Shortcuts

To start a merge discussion, perform the following steps. If the merge is difficult to perform or seems potentially controversial, you can request assistance and feedback atWikipedia:Proposed mergers.

Do not use the discussion procedure described here to propose:

Shortcut

Note thatif the need for a merge is obvious, editors canbe bold and simply do it. Seehow to merge below. Bold merges may be reverted, even if it was labor-intensive to complete, but this edit process andcivil discussion produces better articles. Articles that are young or short, such asstubs differing only in title and wording, should be merged immediately. Articles that have been separate for a long time should usually be discussed first, especially those on controversial topics.

Step 1: Create a discussion

This is usually done on the proposed destination page's talk page. For example, if suggesting thatFoo be merged intoBar, create a proposal in a new section atTalk:Bar. If the destination does not exist, do not create its talk page.

Start a new section and includethe proposal itself, the list of the affected pages, and a merge rationale.A good example is the following section:

If the merge proposal was incorrectly started on the source's talk page, and the proposed destination is unambiguous and exists, any editor can move the proposal to the talk page of the''destination'', to increase its visibility. Use the{{Tl|Moved to}} and{{Tl|Moved from}} templates.== Merge proposal ==I propose merging[[Foo]] into[[Bar]]. I think the content in Foo can easily be explained in the context of Bar, and a merge would not cause any article-size or[[WP:UNDUE|weighting]] problems.~~~~

Notify involved users (optional)

You may optionally notify involved users (e.g. contributors to the source and destination pages), who might not bewatchlisting them. One way is to simplynotify them directly from the merge discussion page:

{{ping|User1|User2|User3|...}} Message text. ~~~~

Alternatively, go to those users' talk pages and start a new section. Make sure to provide a link to the merge discussion.You may use the following standard template to leave a standard message:

{{subst:Mergenote|Foo|Talk:Bar#Merge proposal}}

Please respectneutrality when making invitations to participate in the merge discussion.Votestacking, that is, canvassing support by selectively notifying editors who have a predetermined point of view or opinion, is inappropriate.

Step 2: Tag the relevant pages

These templates shouldnot besubstituted.

To propose a merge of two pages, place the following template at the top of each page or section:

{{merge|OTHERPAGE|discuss=Talk:DESTINATIONPAGE#Merge proposal|date=October 2025}}

If you know which page should be removed, use

{{merge to|DESTINATIONPAGE|discuss=Talk:DESTINATIONPAGE#Merge proposal|date=October 2025}}

on the source page, and

{{merge from|SOURCEPAGE|discuss=Talk:DESTINATIONPAGE#Merge proposal|date=October 2025}}

on the destination page.

If two pages are proposed to be merged into a third destination page that already exists, use

{{merge|OTHERSOURCEPAGE|target=DESTINATIONPAGE|discuss=Talk:DESTINATIONPAGE#Merge proposal|date=October 2025}}

on the source pages, and

{{merge from|SOURCEPAGE1|SOURCEPAGE2|discuss=Talk:DESTINATIONPAGE#Merge proposal|date=October 2025}}

on the destination page.

If two pages are proposed to be merged at a destination page that does not yet exist (destination does not have a talk page), use

{{merge|OTHERSOURCEPAGE|target=DESTINATIONPAGE|discuss=Talk:SOURCEPAGE#Merge proposal|date=October 2025}}

on each source page, choosing one of the source talk pages as the discussion location and ensuring thediscuss parameter directs to this talk page on both source pages.

Please use thediscuss parameter to directto the same talk page. Otherwise, two separate discussions could take place.If thediscuss parameter is not specified, the "Discuss" links lead to the top of each article's Talk page.In{{merge to}},{{merge from}}), it always leads to the destination talk page, but it is still preferable to link to a specific section of the talk page.

In other namespaces

  • Do not use the above templates to propose acategory merge. This should be requested atWP:Categories for discussion, which uses a separate{{cfm}} template.
  • For a merge of pages within "Wikipedia" namespace (titles with the "Wikipedia:" or "WP:" prefix), do not include this prefix in the parameter.
  • When proposing a merge between two different namespaces, these templates won't work because of technical limitations.

Step 3: Discuss the merge

Make sure to followstandard talk page guidelines, which includescivility andstaying focused on the content, not on the involved editors, usingthreaded discussion formatting,not biting newcomers, and being clear and concise.

In many cases, a hybrid discussion/straw poll is used, but remember thatpolling is not a substitute fordiscussion. Example formatting:

*'''Merge''' – <insert reason for supporting merge here>~~~~*'''Don't merge''' – <insert reason for opposing merge here>~~~~

Step 4: Determine consensus and close the merge discussion

Shortcut

During discussion, arough consensus may emerge to proceed with the merge.Any user, including the user who first proposed the merge, may close the discussion and move forward with the merge if enough time (normally one week or more) has elapsed and therehas been no discussion or if there is almost unanimous consensus to merge. Closing of merge discussions differs fromclosing of requested move discussions in that closings of uncontroversial merge discussions byinvolved users are allowed. Admin tools are not needed unless page protection prohibits editing.

In more unclear, controversial cases, the determination that a consensus to merge has or has not been achieved should be made by an editor who is neutral and not directly involved in the merge proposal or the discussion. The discussion can be posted atWP:Proposed mergers to get some help. If necessary, a request that an administrator, who is notinvolved, close the discussion can be made at theRequests for Closure noticeboard. If a consensus is formed against the merge shortly after it was performed, it can easily be reversed.

To close a merge proposal discussion, the{{Discussion top}} and{{Discussion bottom}} templates are used in the following manner:

== Merge proposal =={{Discussion top|result=The result of this discussion was... .~~~~}}The merge proposal...* and discussion...* ...{{Discussion bottom}}

If there is consensus to merge

After closing the merge proposal discussion, remove the{{Merge to}} template from the source page and the{{Merge from}} template from the destination page. Replace both with the{{Being merged}} template, which is used in the following manner:

{{Being merged| spacetype= <"article/template/section", depending on what is being merged>| discuss= <closed merge discussion, entered as "Talk:Page name#Section name">| target= <other page, entered as "Page name">| dir= <"to/from", depending if it is the destination page or the source page>| date= <date merge was accepted, entered as "a date string" (according to preference)>}}

If there is consensus against merging or no consensus

After closing the merge proposal discussion, remove the{{Merge to}} template from the source page and place the{{Old merge}} template on the corresponding talk page in the following manner:

{{Old merge| otherpage= <destination page, entered as "Page name">| date= <date merge was proposed, entered as "a date string" (according to preference)>| result= <result of discussion, entered as "'''No consensus'''" (with boldface markup)>| talk= <merge discussion, entered as "Talk:Page name#Section name">| URL= <permanent link, entered as "U_R_L" (with underscored spaces)>}}

Then, remove the{{Merge from}} template from the target page.

Step 5: Perform the merge

Shortcuts
For information on moving pages, seeHelp:Moving a page.

The main reason that the merge backlog includes thousands of articles is because the people who support the merge neglect to undertake this final step.Any editor, including the editor who originally proposed the merge, is permitted to perform a merge in accordance with consensus. Merging pages doesnot require intervention from an administrator. To merge articles, follow the steps below.

  1. Copy all or some of the content from the source page(s) andpaste the content in an appropriate location at the destination page.Don't just redirect the source page without copying any content if any good content from the source page exists. Publish the edit, leaving the following edit summary (a link to the source article isrequired by copyright):
    Merged content from [[source page]] to here. See [[Talk:merge discussion section]].
    Ideally, do any necessary copyediting and rearranging in a separate, second edit rather than when you first paste the moved text (to simplify attribution). In practice, this means: Copy and paste all the content you want to transfer; publish the page with the required edit summary (even if it duplicates parts or looks a bit messy at this stage; you can use{{In use}} or{{Inuse-section}} if you want to let others know you'll be fixing it right away); then edit the page a second time to clean it up.
  2. Redirect the source page whose content was just merged by replacingeverything with the following:
    #REDIRECT [[destination page]]{{rcat shell|{{R from merge}}}}
    Or if the content was merged to a single section, the following:
    #REDIRECT [[destination page#section]]{{rcat shell|{{R from merge}}{{R to section}}}}
    Publish the page, leaving the following edit summary:
    Merged content to [[destination page#section]]. See [[Talk:merge discussion section]].
  3. Reconcile talk page tags. If the source page has a talk page:
    • Move any{{merged-from}} and{{copied}} templates to the destination page's talk page.
    • Reconcile{{WikiProject ....}} templates: copy them from the source page to the destination and remove duplicates (look out for alternative templates; e.g.{{WikiProject Software|Computing=yes}} is the same as{{WikiProject Computing|Software=yes}}). Once copied, change the source article WikiProject templates so that they contain|class=redirect (even for WikiProjects that do not yet support a redirect class); this does not have to be done if{{WikiProject banner shell}} is being used, since that template will automatically choose the class.
  4. Optionally:Tag the destination page's talk page with{{merged-from|source page name|date}}, and the source page's talk page with{{merged-to|destination page name|date}}. Place these tags at the top of the talk pages.
    Do not add a new merge-from template to the destination talkpage if the merger is the result of anWP:AfD discussion, andTemplate:Afd-merge from has already been placed on the destination talkpage.
    As an alternative, experienced users can add{{copied|from=|from_oldid=|to=|to_oldid=|to_diff=|date=}} to the top of both talk pages.
  5. Optionally:Fix anydouble redirects found atSpecial:WhatLinksHere. A bot automatically fixes this problem but it may take a day or two.
  6. Check fornon-free images (or other files). Examples:a book cover,a poster, a logo, etc. The description page of such an image will have a red copyright icon and anon-free use rationale (a summary box withNon-free use rationale in the title, or aFair use section) – the article title mentioned in such a rationale should be updated. This is required under thenon-free content criteria.
  7. Remove the relevant{{Merging}} template from the destination article, if it still exists.

Note 1: Most merged articles are not good candidates for merging of page histories because they have beenedited in parallel and the collation of their edit states would create unhelpful and/or misleading diffs. In most cases, no request for a history-merge should be submitted.

Note 2: Merging should not be confused with acut-and-paste move, where the former refers to joining content across different pages withexisting content, and the latter refers to copying and pasting the entire content of an article to a new name (where there isno or little content at the target name).

Merge as a result of a deletion discussion

See also:Wikipedia:Deletion policy § Alternatives to deletion

InArticles for Deletion (AfD) discussions, editors may suggest that thearticle(s) nominated for deletion bemerged to an appropriate article. If there is a rough consensus for a merge at the end of a deletion discussion, the following template is placed at the top of the nominated article:

{{tlx|Afd-merge to|destination article|debate name|debate closure date}}

Similarly, the following template is placed on the destination article's talk page:

{{tlx|Afd-merge from|nominated article|debate name|debate closure date}}

This informs users involved in those pages that content is to be merged as a result of a deletion discussion. It is theinvolved editors' job, not theclosing administrators' job, to perform the merge. Proceed in the manner described above. See alsoWikipedia:Merge what?, an essay encouraging not to just vote "merge" in AfD discussions.

See also

Articles to be merged
(refresh)
Subtotals
January 202516
February 20257
March 20255
April 202528
May 202573
June 202567
July 2025114
August 2025228
September 2025260
October 2025299
Undated articles0
1,097
Jump to a random article from the merge backlog!
   Merge a random article!

Merge templates

Main pages:Wikipedia:Template messages/Merging andCategory:Merge templates
Article page
PAM notice
User talk page
PAM discussion notifications
  • {{Mergenote}}(PAM notification to user talk page)
Discussion page
PAM templates
User talk page
PAM process notifications
Article source talk page
PAM notice
  • {{Merge done}}(Merge after discussion notice; for source talk page)
  • {{Merge to}}(PAM merge request; for source page; use{{Merge from}} on destination talk page)
  • {{Merged-to}}(Post PAM merge completed; for source talk page)
  • {{Being merged}}(Source page merging in action notice)
  • {{Mfd-merge to}}(Post MfD merge needed; for source talk page; use{{Mfd-merge to}} on destination page)
  • {{Old merge}}(1st and subsequent nominations)
Article destination talk page
PAM notice
Miscellaneous
PAM misc.

Other guides

About Wikipedia (?)
Help for readers (?)
Contributing
to Wikipedia (?)
Getting started (?)
Dos and don'ts (?)
How-to pages and
information pages (?)
Coding (?)
Directories (?)
Retrieved from "https://en.wikipedia.org/w/index.php?title=Wikipedia:Merging&oldid=1318664625"
Categories:
Hidden category:
[8]ページ先頭
©2009-2025 Movatter.jp