Wikipedia:Articles for deletion/Implementing the PAM–AfD merge
From Wikipedia, the free encyclopedia
Not done
| Task name | Prio-rity | Status | Dependent on... | Description | Plan | Who | Discussions |
|---|---|---|---|---|---|---|---|
| Update {{afdm}}, {{afd}}, {{afdx}}, {{afdn}} parameters | High |  In progress | — |
|
oklopfer, ScrubbedFalcon, Chaotic Enby | ||
| Clear out PAM backlog | Medium | In progress | — | Clear out the PAM backlogs Category:Articles proposed for merging and Category:Articles with consensus to merge | Continue as usual, slowly closing all open discussion and performing merges with consensus. Move all new PAM discussions to AfD. | The latter is being done by FaviFake | |
| Turn PAM {{merge to}} template into wrapper of {{AfDM}} | Medium |  In progress(blocked) | Update afd parameters | Turn {{merge to}} and {{merge}} into wrappers of the {{AfDM}} template. Details are in the TfD consensus (merge w/ target ≈ merge to w/ 1 or target). Turn the various |talk= parameters into aliases of |afd= |
|
ScrubbedFalcon, ChaoticEnby, oklopfer | AFD#{{Merge to}} wrapper rewrite |
| Add extra steps to XFDcloser for merges | Very high | In progress |
Twinkle AfD merge option | Update and remove leftover {{Merge from}} templates after closing an AfD as "merge" | ??? | ||
| Allow making a bundled merge nomination using Twinkle directly | Medium |  Ready,not started |
— | Currently, Twinkle can only nominate one thing at a time. For example, if one were to nominate more than one article for merging at a time, one would have to make the first nomination and then manually tag the other pages. Twinkle should do it automatically | |||
| XFDcloser afd-merge params | High | In progress | Updates to afd-merge templates | Update XFDcloser to use the new afd-merge params |
|
oklopfer | |
| Rewrite PAM {{merge from}} and {{being merged from}} template | Medium | In progress |
— |
|
Being merged backlog needs to be minded when making these changes; in-use templates may need param updates (can be done with AWB/JWB) | ||
| Deprecate redundant PAM templates | Medium | In progress (blocked) |
|
|
Note that w/ and w/o to currently function differently; backlog needs clearing before this can be done. Compare:
|
||
| Remove {{Merge}} options from Page Curation | Medium | Not started |
— | Remove the historical {{Merge}} tags from the Curation Toolbar, just like Twinkle did | |||
| Update wording of Module:Old XfD multi and module:Copied | Low | In progress |
— | Module:Old XfD multi and module:Copiedcurrently default to saying "nominated for deletion" even though the articles are actually being nominated for merging (example) |
|
Trialpears | {{Old XfD multi}}#Change default wording following PAM–AFD merge |
| Update wording of SDZeroBot talk page notices | Medium | Not started |
— | Currently notifies editors about deletion even if nominated for merging. | Make it use all 4 cases (see {{Afd notice/testcases}} | User:SD0001 | SDZeroBot#Necessary update following PAM merger |
| Merge the PAM and
AfD-merge categories |
Medium | Not started | — | Once the PAM backlogs are cleared, the distinction of Category:Articles with consensus to merge following AfD discussion will no longer be necessary. | Update all templates that currently add pages to the "... following AfD discussion" categories to use the Category:Articles with consensus to merge, and delete the former AfD-merge categories once they're empty. | ||
| Update all documentation pages of the various Merge templates | Low | Not started |
Everything else, ideally | Most /doc pages are out of date or too short | Update them, maybe by transcluding parts of WP:MERGE like in {{Merge/doc}} | FaviFake or anyone else! | |
| Clear {{Merge portions from}} backlog | Low | Not started | — | Cleanup the pages using the template so that it can be deprecated | Undecided | {{Merge}}#AfD parameter | |
| Consider creating {{afd-merged-to}} | Low | Not started | Update {{afd-merge to}} params | Consider creating a partner template parallel to {{merged to}} and {{afd-merged-from}}. May be decided to stick with the current {{old XfD multi}}&{{merged to}} combination instead. | Undecided | TfD#Merge templates | |
| Deal with the draft merge backlog | Low | Not started |
? | We have a huge backlog of pages in the Draft: and User: namespaces. These drafts and user drafts were covered by PAM and so they were tagged. Since MfD is only for deletion and PAM doesn't exist anymore, do we just remove the tags from all of them, even if they have a talk page discussion attached to them? | We should probably add some tracking categories and figure out what to do with the pages tagged. After they've all been cleaned up in some way, the templates should probably show a big error message when placed in these namespaces? (or in all namespaces except articles and drafts?) | {{Merge}}#Include draft merge proposals in the merge backlog | |
| Improve display of {{multiple}} {{merge from}} templates | Very low |  In discussion |
— | Is it possible for templates to display a different message when inside {{multiple}}? | In discussion |
||
| Decide what to do with the {{Old merge}} template | Low | — | Does it duplicate {{old XfD multi}} now that merge nominations can only be made at AfD? | Maybe if the date provided is after March 2026, it should show an error inviting the user to use {{old XfD multi}} instead? | |||
| Rename "Articles proposed for merging" cats | Low | Not started |
— | Merge proposals was the old name, now we nominate articles for merging. | Rename to Articles nominated for merging | ||
Done
| Task name | Prio-rity | Status | Dependent on... | Description | Plan | Who | Discussions |
|---|---|---|---|---|---|---|---|
| Add Twinkle AfD merge option | High |  Done |
AfD/Dated template | Add merging as option to Twinkle AfD module |
|
Novem Linguae | Twinkle#Updates to AfD backend |
| Update instructions at AFD1 and MERGE | Medium | Done |
— | Update instructions (manual and Twinkle) and streamline AFD page, and clarify the instructions for bundling merge nominations | FaviFake, ScrubbedFalcon | ||
| Clarify if merge noms can end as delete | Medium | Done |
? | Clarify if articles nominated for merging at AfD can be deleted as a result of that discussion. If no, then update instructions on participating in and closing discussions. | Decided to add clarification to all of the versions of the AfD templates | ScrubbedFalcon, Chaotic Enby | AFD#Can merge discussions at AfD close as Delete? |
| Unnamed parameters backlog | High | Done |
— | Clear out Category:AfD merge templates using unnamed parameters | Use regex replace with AWB/JWB | oklopfer | AFD#Implementing the template updates |
| Where should MERGEREASON go? | Very low | Done |
— | Should MERGEREASON be moved elsewhere? | It shouldn't. | Deletion policy#Adjusting ATD-M | |
| Deprecate unnamed parameters on afd-merge to/from and afd-merged-from | High | Done |
Unnamed parameters backlog | Deprecate the old usage of unnamed parameters on the afd-merge series templates to allow repurposing for multi-targeting/sourcing | oklopfer | ||
| Update {{afd-merge to}} and {{afd-merge from}} params | High | Done |
Unnamed parameters backlog | Update the parameters to match those of {{merge to}}+{{being merged to}} and of {{merge from}}+{{being merged from}} respectively | Turn current usage of unnamed params into named ones, then import usage from the old templates | oklopfer | AFD#Planning the template updates |
| Update {{afd-merged-from}} params | High | Done |
Unnamed parameters backlog | Update the parameters to match those of {{afd-merge from}} to avoid breakage when the bot auto-replaces the template post-merge | Turn current usage of unnamed params into named ones, then import usage from the old templates | oklopfer | |
| Option to block redirects in {{pagelist}} | High | Done |
{{pagelist}} needs to have a |noredir= parameter to maintain the usage of {{noredir}} in the afd-merge templates while also allowing for multi-page listing |
Module:Pagelist/sandbox updated, awaiting template editor approval and merge | oklopfer | Template talk:Pagelist#Edit request 4 June 2026 | |
| Add XFDcloser SOFTMERGE option | Low | Done |
None! | Add the option to close a discussion as soft merge rather than merge. You should be able to just tick the "soft" check box to do a soft merge closure. | Novem Linguae | XFDcloser#Extra step needed on merge closes | |
| Decide and implement the nomenclature for failed AfD merge discussions | Very low | Done |
Should a failed merge proposal be closed as keep or not merged? If the latter, XFDcloser will have to be updated to somehow support it. | "keep" | Deletion process#The opposite of “merge(d)” is “not merged” | ||
| PROMERGE instructions | Low | Done |
None | Clarify the instructions at PROMERGE on edit summaries to make sure that the instructions are clear for both boldmergers and merges that result from a discussion and that all necessary links are included. | Being discussed at WT:Merging | FaviFake, ScrubbedFalcon | Wikipedia talk:Merging#Promerge edit summary instructions |
| Decide what to do with the {{Consider merging}} template | Low | Done | None | Create a consider merging template similar to {{Notability}} | ScrubbedFalcon | ||
| Decide whether AfD can be closed as SOFTMERGEwithout being relisted if previously kept | Very low | Done |
None | If a merge was actively considered in previous AfD discussion (for example as an alternative to deletion) a soft merge closure will not usually be appropriate. |
Deletion process#Does soft merge apply? |