GitHub lets the Triage role archive pull requests, not just admins

On October 8, 2026, GitHub changed the access rules for archiving pull requests. Users with the Triage role or higher can now archive and unarchive them. Until now, only repository administrators had this permission. Among GitHub's five standard roles (Read, Triage, Write, Maintain, Admin), the bar dropped from the top tier to the second from the bottom. It is a small change to one of the platform's busiest workflows.

What exactly changed

The announcement in the GitHub Changelog is brief. Previously, archiving a PR required administrator rights, so trusted triagers had to pass even routine cases to administrators. The announcement text, in the version available to us, cuts off at that sentence. It gives no implementation details, such as how archived PRs appear in search and filters, or which events show up in the audit log. Check GitHub's documentation for those.

The rule now works in both directions: a user with the Triage role can both move a PR to the archive and bring it back. That matters. A triager can fix an erroneous archiving without hunting down an administrator.

Why the access threshold matters

GitHub created the Triage role for people who sort through the incoming flow. They apply labels, assign owners, close duplicates and reopen issues. They cannot push code to the repository. It is a natural role for volunteers in open-source projects, and for support engineers or QA specialists in corporate teams.

Before the change, there was a gap. A triager could see an outdated or abandoned PR and close it, but could not remove it from the workspace. For that, they had to message an administrator. Small projects usually have just one administrator, and such requests quickly become a bottleneck. Now routine queue cleanup stays at the level where decisions about the queue's contents are made.

There is also some indirect context. Tools such as coding agents make opening PRs cheaper, and queues are growing in many repositories. GitHub does not mention this connection in its announcement; it is our observation. But the more PRs are created automatically, the more each extra handoff between roles costs.

Key details at a glance

• Announcement date: October 8, 2026.
• Who has access: the Triage role and above (Triage, Write, Maintain, Admin).
• Operations: archiving and unarchiving pull requests.
• Previously: repository administrators only.
• Source: GitHub Changelog.

How to use the change in your team

First, check who in your repository has the Triage role. If you handed it out only for labels and assignments, those people now have one more action available. For most teams this is acceptable, but projects with a strict process should announce it in advance.

Next, record the archiving criteria in CONTRIBUTING or an internal guide. For example: PRs with no activity beyond a set period, duplicates, and PRs abandoned by their author. Without a rule, different triagers will make different decisions, and "why did my PR disappear" questions will come up more often.

Finally, if you have automation around PRs (bots, dashboards, review-speed reports), check how they handle archived requests. Developers who measure PR lifetime should decide in advance whether archiving counts as closing. GitHub is unlikely to tell you how to handle this in your particular workflow.