Tips for writing good bug reports and feature requests:
Include the affected article name and a diff.
Include a screenshot.
For bugs, include the exactsteps to reproduce the bug. Bugs need to be reproducible.
We will use this information to create a ticket onGitHub, which is our todo list for volunteer developers. For most tickets, expect them to take a long time (months). They will need to attract the interest of a volunteer developer, then go through code review, then get merged to master, then get deployed.
Twinkle has detailed documentation located atWP:TW/DOC.
Please donot use this page to testadvance reporting and vetting (ARV),speedy deletion (CSD),nominate for deletion (XFD), orrequest page protection (RPP), as these notify administrators.
I'm just curious about what this means, and how it notifies administrators. While I have sometimes "tested" the templates in the editor in sandbox pages/user space, I have not actually been publishing the changes; only viewing the preview before abandoning the edit(s).RaptorsFan2019 (talk)15:51, 30 September 2025 (UTC)[reply]
It doesn't mean "notify" as in "ping" or any direct 1-1 notification.
ARV lets you automatically file reports toWP:AIV,WP:SPI,WP:AN/3, etc., and does so by directly editing those pages. Some administrators monitor those pages.
RPP files a report atWP:RPP, which is monitored by some administrators.
CSD adds a few categories to the page which some administrators monitor.
I think "Please do not use this page..." is referring to the fact that some Twinkle reporting functions make edits to both the test page (the sandbox in this case) and a noticeboard. The noticeboard edit is what notifies admins. Hope this helps. –Novem Linguae(talk)18:02, 30 September 2025 (UTC)[reply]
I ran into a case today where an admin used the "Nuke" feature to delete dozens of articles but the Nuke feature doesn't delete either Talk pages or redirects of those articles so these had to be deleted separately later which is quite a pain. And I was remembering several times where I came here asking about a similar feature on Twinkle because Twinkle deletes articles/drafts/pages but doesn't delete the talk pages of any redirects that exist. You all were working on this feature and I wanted to follow-up and ask how it was coming along. Is it still a change at somw point in the distant future? You would think that this would be an uncommon situation but it actually comes up every day.
Coding Twinkle to handle multi-blocks would be complicated and would need additional engineering time. So as a band aid measure, we have it display a link toSpecial:Block, which can handle multi-blocks. A patch to Twinkle adding support for multi-blocks would be welcome. –Novem Linguae(talk)22:28, 1 October 2025 (UTC)[reply]
Why delay in merging pull requests by maintainers?
We see fairly frequent bug reports and feature requests in this page. There are several issues in the code that need improvement, which volunteers are willing to help. In spite of this several pull requests are pending approval without any comment, many from several months ago. I understand maintainers are volunteers as well, but it is not good to ignore pull requests for so long and discourage those who are willing to contribute code.2409:40F2:314C:15B9:8000:0:0:0 (talk)15:03, 10 October 2025 (UTC)[reply]
Sorry about that. I'm a volunteer and I have been busy. It's on my todo list to spend like a week and clear out the PR queue as soon as I get some free time. PRs take awhile to approve because I manually test each one, and that's not very fun. And reading code is a high-brainpower activity. However I think the manual testing makes sense and must be done because 1) Twinkle has like 40,000 users or something so any bugs will affect a lot of people, and 2) we have a lot of first time contributors / newer contributors who write patches in this repo and they don't always manually test them on testwiki before submitting their PR.
If it matters I'll take whatever you can give, whenever you can give it. You'reeverywhere helping out with a ton of our vital tools, which is great, but if it's too much then I'd rather wait another week or two. Enjoy WCNA!Primefac (talk)20:34, 11 October 2025 (UTC)[reply]
Hi, I just used the G15 speedy deletion for the first time, but it seems that it didn't put a notice on the user talk page? Is this intentional?Fram (talk)15:22, 27 October 2025 (UTC)[reply]
Interesting bug. This has to do with the Twinkle config atUser:Fram/twinkleoptions.js only writing true values and assuming anything absent is false. But in reality, it should also write the false values, that way it can assume anything absent should use the default value.
This is a hard bug to fix properly. But it has an easy workaround. You can just visit your Twinkle preferences -> "Notify page creator when deleting under these criteria" -> tick G15 -> Save. Hope that helps. –Novem Linguae(talk)19:04, 27 October 2025 (UTC)[reply]
Thanks! Perhaps in the preferences, an option "all" can be added to overrule the individual toggles of when to notify/not to notify? Not mega-important, but I can imagine that others have the same issue and perhaps don't even realise it.Fram (talk)19:17, 27 October 2025 (UTC)[reply]
Just to be clear, this refers to when I'm actuallydeleting a page, not just requesting speedy (ie. the 'Tag page only, don't delete' box isunselected).
I do have the 'Notify page creator of page deletion' box selected by default.
And before anyone asks, I also have the page creator notification selected in my Twinkle prefs for G15 (in fact, all bar R2/R4/X3), so Novem's suggested workaround won't help.
"CSD U5 has been repealed. It has been replaced with U6 (procedural deletion of some previously U5-eligible pages) and U7 (a much narrower reworking of U5). Please see those criteria to determine if either applies." just appeared on something Ione normally tags as U5 🇵🇸🇺🇦 FiddleTimtrentFaddleTalk to me 🇺🇦🇵🇸15:05, 30 October 2025 (UTC)[reply]
I'm giving this high priority and carved out some time to work on it today. Will do a round of code review with Chaotic Enby to finish this up, then will merge and deploy it. –Novem Linguae(talk)23:44, 2 November 2025 (UTC)[reply]
Another important note regarding the uw-multipleTAs template: Twinkle leaves a pre-filled "Vandalism using multiple IPs [on page name]." edit summary when placing the uw-multipleTAs template. That edit summary should be changed to "Disruption using multiple temporary accounts [on page name].". — AP 499D25(talk)13:16, 4 November 2025 (UTC)[reply]
It is obvious that temporary accounts starting with~2025- are unregistered. It might be best if theTwinkle • Welcome user menu only listed theIP user welcomes for temporary accounts, perhaps renamed toTemporary account welcomes.Peaceray (talk)16:56, 4 November 2025 (UTC)[reply]
@Thebiguglyalien. Weird. I couldn't get{{Disputed}} to show up as ticked when I tested this on testwiki.Diff. I also don't see it in the wikicode. So that's interesting that you were able to get an edit summary that included it.
Can we get the block evasion block reason/template added for accounts as well as IPs? Doesn't really make sense to block temp accounts as socks when it's essentially block evasion as an IP.ScottishFinnishRadish (talk)13:33, 5 November 2025 (UTC)[reply]
@ScottishFinnishRadish. Hey there. Can you help me spec this out? Is this a request to add a template to the "TW -> Block -> Template options -> Choose talk page template" dropdown, or something else? If so, which template exactly should be added? Thanks. –Novem Linguae(talk)21:24, 5 November 2025 (UTC)[reply]
Since jquery.ui is now deprecated, do we have a plan to migrate Twinkle to use Codex in the future? Or it will still use jquery.ui?Nvdtn19 (talk)14:53, 9 November 2025 (UTC)[reply]
Is this just changing the template wording? If so, then the changes will probably be invisible to Twinkle and have little chance of breaking it. Should be OK to Closing without action –Novem Linguae(talk)16:10, 10 November 2025 (UTC)[reply]
This may have been covered elsewhere, but I've just left a welcome note on a temp account, and notice that it still recommends creating an account in order to hide the user's IP Address. I guess the text just needs updating?
You are welcome to edit without logging in; however, creating an account is free and has several benefits (for example, the ability to create pages and upload media). An account also has more protection against revealing your IP address.
I don't know where the best spot is for this but it might be useful to add the ability to include multiple temporary accounts in the ARVwp:AIV feature for users withwp:TAIV rights to be able to report when the same person is vandalizing from multiple temp accounts without revealing the IP address. --Lenny Marks (talk)14:53, 26 November 2025 (UTC)[reply]