GitHub closes the draft loophole and lets triagers archive pull requests
Victoria Shinder2 min readGitHub shipped two small moderation changes on 8 October, both aimed at the same problem it names directly: maintainers "are seeing more low-quality contributions in their repositories".
1. Drafts can count toward pull-request limits. Repositories that cap how many open pull requests a user may have could not stop the same user from opening any number of draft pull requests — drafts did not count. Maintainers can now configure the limit to include drafts. GitHub's reasoning is the cost of each spam PR beyond the PR itself: notifications, clutter, and CI runs that a draft can still trigger.
2. Triagers can archive pull requests. Archiving — the usual action for spam, duplicates and abandoned PRs — used to be limited to repository administrators, so projects that delegate queue hygiene to people without write access had to escalate every case. Now anyone with the triage, write, maintain or admin role can archive and unarchive. GitHub also tightened what archiving does:
- archiving closes the pull request and makes the conversation read-only;
- new comments, reactions and automated comments are blocked while it is archived (previously admins could still comment on a locked thread);
- archived PRs are hidden from public view and stay visible to triage-and-above users — GitHub added that clarification on 9 October;
- unarchiving restores commenting but does not reopen the PR.
Why it matters. The first change removes a cheap way around an existing control; the second moves the action to the people who actually do triage, without giving them the right to change code or toggle a conversation's lock. For projects drowning in AI-generated drive-by PRs, the practical step is to review the repository's pull-request limit setting, switch on draft counting, and give the triage role to the people who already sort the queue. One thing to check first: if your CI runs on draft PRs, a single user's drafts were a cost you were paying even with a limit in place.
Sources: GitHub Changelog, "Draft pull requests count toward pull request limits", 8 October 2026 — https://github.blog/changelog/2026-10-08-draft-pull-requests-count-toward-pull-request-limits ; GitHub Changelog, "Triage role users or higher can now archive pull requests", 8 October 2026 — https://github.blog/changelog/2026-10-08-triage-role-users-or-higher-can-now-archive-pull-requests