Epstein Files Full PDF

This is an information page. It is neither an encyclopedia article nor one of Wikipedia'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 of consensus and vetting.

Shortcuts H:MH:M WP:MERGEWP:MERGE

A merge or merger 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 a redirect 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! Otherwise, the merge should be first proposed and discussed, as detailed below. When performing a merge, remember to attribute copied content, as required by Wikipedia's copyright license. At minimum, this means including Merged content from [[SOURCEPAGE]] in your edit summaries. See how to merge below for details.

There are several good reasons to merge pages:

1. Duplicate: There are two or more pages on the same subject and with the same scope, also known as redundant content forks. If the content fork was unjustified, the article created more recently should be merged into the older one. If a duplicate article was created recently, it may also be a candidate for A10 speedy deletion.
2. Overlap: There are two or more pages on related subjects that have a large overlap and might be WP: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 on flammability.
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 the general notability guidelines, or more specific criteria, so merging is an alternative to deletion. While this can also be implemented through the articles for deletion process, merging directly may be more efficient. For example, parents or children of a celebrity who 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 also Wikipedia:Notability (fiction).

Merging should be avoided if:

1. the resulting article would be too long or "clunky";
2. the separate topics could be expanded into longer standalone (but cross-linked) articles;
3. the pages are category or templates, which should be discussed at Categories for discussion and Templates for discussion respectively.

If the need for a merge is obvious, editors are encouraged to be bold and simply do it themselves. See how to merge below. Young or short articles and stubs that only differ in wording should be merged immediately. Longer articles that have been separate for a long time are usually discussed first, especially if they are about controversial topics. If the merge is difficult to perform or is potentially controversial, you can request assistance and feedback at the Proposed article mergers noticeboard.

While bold merges may be reverted entirely, the process and the discussion after the revert results in better articles. To start a merge discussion, perform the following steps.

This is usually done on the proposed destination page's talk page. For example, if suggesting that Source page be merged into Destination page, create a proposal in a new section at Talk:Destination page. If the destination does not exist, do not create its talk page.

Create a new topic and include the list of the affected pages and a merge rationale. For example:

== Merge proposal ==
I propose merging [[SOURCEPAGES]] into [[DESTINATIONPAGE]]. I think the content in SOURCEPAGE can easily be explained in the context of this article, and merging them would not cause any article-size or [[WP:UNDUE|weighting]] problems. ~~~~

If a merge proposal has been incorrectly created on the source's talk page and the proposed destination is unambiguous and exists, any editor can move the discussion to the talk page of the destination page, to increase its visibility. Use the {{Moved to}} and {{Moved from}} templates.

Optionally, you can notify contributors to the pages involved. One way is to ping them in a comment on the merge proposal, such as {{ping|User1|User2|User3|...}} Notifying contributors to the articles. ~~~~. Alternatively, create a new topic on those users' talk pages with {{subst:Mergenote|PAGENAME|Talk:PAGENAME#Merge proposal}}. Respect neutrality when making invitations to participate in the discussion; selectively notifying editors is not allowed.

To propose merging:

• two articles together: place {{Merge to|DESTINATIONPAGE|discuss=Talk:DESTINATIONPAGE#Merge proposal|date=February 2026}} at the top of the source page, and {{Merge from|SOURCEPAGE|discuss=Talk:DESTINATIONPAGE#Merge proposal|date=February 2026}} at the top of the proposed destination article or section.
  • If you don't already know which article should be merged and which should remain, place {{Merge|OTHERPAGE|discuss=Talk:PAGE#Merge proposal|date=February 2026}} on both pages.

• many articles into an existing article: place {{Merge|OTHERSOURCEPAGES|...|target=DESTINATIONPAGE|discuss=Talk:DESTINATIONPAGE#Merge proposal|date=February 2026}} on all source pages, and {{Merge from|SOURCEPAGE1|SOURCEPAGE2|...|discuss=Talk:DESTINATIONPAGE#Merge proposal|date=February 2026}} at the top of the proposed destination article or section.

• many articles into a page that doesn't exist yet: place {{Merge|target=DESTINATIONPAGE|SOURCEPAGE1|SOURCEPAGE2|...|discuss=Talk:SOURCEPAGE#Merge proposal|date=February 2026}} on each source page.

Always use the |discuss= parameter to link to the same discussion. Otherwise, two separate discussions could take place. If the parameter is not specified, the notices 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. (When proposing a cross-namespace merge, these templates won't work.)

Make sure to follow standard talk page guidelines and be clear and concise. Usually, a hybrid discussion/straw poll is used, but remember that polling is not a substitute for discussion. Example:

* '''Merge''' – The scope of the articles is the same.  ~~~~
* '''Don't merge''' – The resulting article would be too long. ~~~~

During discussion, a rough 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 the consensus is clear or there has been no discussion. Closing of merge discussions differs from closing of requested move discussions in that closings of uncontroversial merge discussions by involved users are allowed.

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 listed at the Proposed article mergers noticeboard to attract the attention of more editors. If necessary, you can request that an uninvolved editor close the discussion at the Closure requests noticeboard. If a consensus is formed against the merge shortly after it was performed, it can easily be reversed.

To close a merge discussion, use the {{Discussion top}} and {{Discussion bottom}} templates.^[a] Then:

• If the discussion is closed with consensus to merge, change the {{Merge to}} tag to {{Being merged to}} in the source page, and change {{Merge from}} to {{Being merged from}} in the destination page. They should remain tagged until the merge is fully performed, so that they are listed on the relevant backlog.
• If the discussion is closed with consensus against merging or no consensus, remove all the {{Merge}} templates from the destination and source pages, linking to the discussion in your edit summary. Optionally, you can also place {{Old merge}} on the corresponding talk pages.^[b]

The main reason that the merge backlog includes hundreds 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 does not require intervention from an administrator. To merge articles, follow the steps below.

1. Copy all or some of the content from the source page and paste the content in an appropriate location at the destination page. If the source page contains any good content, copy it over instead of just redirecting it. Remove the {{Merge}} or {{Being merged}} templates from the article. Publish the edit, leaving an edit summary similar to the one below (linking to the source article is required by copyright):

   Merged content from [[SOURCEPAGE]]. See [[Talk:DESTINATIONPAGE#Merge proposal]].
   

   Ideally, do any necessary rearranging and copyediting in a separate edit, to simplify attribution. Copy and paste the content to transfer and immediately publish the page with the edit summary above, even if it duplicates some parts. (You can place {{In use}} or {{Inuse-section}} to let editors know you're currently working on it.) Then, edit the page a second time to clean it up.
2. Redirect the source page whose content was just merged. To do this more quickly, you can install the easy-merge script and follow the instructions on its documentation. To do it manually, replace everything in the source page with:

   #REDIRECT [[DESTINATIONPAGE]]
   {{Redirect category shell|
   {{R from merge}}
   }}
   

   Or, if you merged the content to a section:

   #REDIRECT [[DESTINATIONPAGE#Section]]
   {{Redirect category shell|
   {{R from merge}}
   {{R to section}}
   }}
   

   Then publish your changes, using an edit summary such as:

   Merged content to [[DESTINATIONPAGE]]. See [[Talk:DESTINATIONPAGE#Merge proposal]].
   

3. Reconcile talk page tags. If the source page has a talk page:
   • Move any previously added {{Merged-from}} and {{Copied}} templates to the destination page's talk page.
   • Reconcile the various {{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}}).
4. (Optional) Tag the talk pages with the relevant templates, for posterity. This action is perfomed automatically when using the easy-merge script. To do it manually, place {{Merged-from|SOURCEPAGE|February 2026}} atop the destination's talk page and {{Merged-to|DESTINATIONPAGE|February 2026}} atop the source's talk page.

   However, do not add them if the merge is the result of an AfD discussion and the {{Afd-merge from}} template is already on the destination's talk page.

   Experienced users can alternatively add {{Copied|from=|from_oldid=|to=|to_oldid=|to_diff=|date=}} to the top of both talk pages. This is especially useful to replace many similar merge tags and collapse them into one.

5. (Optional) Fix any double redirects found at Special:WhatLinksHere. A bot does this automatically, but it may take a day or two.
6. Check for non-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 a non-free use rationale (a summary box with Non-free use rationale in the title, or a Fair use section) – the article title mentioned in such a rationale should be updated. This is required under the non-free content criteria.

In Articles for deletion discussions, editors may suggest that the articles nominated for deletion be merged to an appropriate article as an alternative to deletion. 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:

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

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

{{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 the involved editors' job, not the closing editors' job, to perform the merge. Proceed in the manner described above. See also Wikipedia:Merge what?, an essay encouraging not to just vote "merge" in AfD discussions.

• Wikipedia:Proposed article mergers is a noticeboard for discussions about merging articles
• Category:Articles proposed for merging lists pages that have been tagged for merging but haven't reached consensus
• Category:Articles with consensus to merge lists pages with discussions closed with consensus to merge.
• WikiProject Merge was used to coordinate the clearing of the merge backlog.

Jump to a random article from the active mergers backlog!

   Merge a random article!

• Wikipedia:Splitting
• Wikipedia:Moving a page
• Wikipedia:Section move
• Wikipedia:Content forks, on duplicated content in acceptable and unacceptable cases
• Wikipedia:Copying within Wikipedia, more details on copyright issues
• Wikipedia:Merge and delete, on deleting the source page instead of redirecting
• Wikipedia:History merging, if they have not been edited in parallel, some merged articles may also be history merged
• Wikipedia:Articles for merging, a failed proposal for a different discussion process