Triage Role Users Can Now Archive Pull Requests on GitHub

What changed?

GitHub now allows users with the triage, write, maintain, or admin roles within a repository to archive and unarchive pull requests. Previously, only repository administrators could perform these actions. Additionally, archiving a pull request now automatically closes it and makes the conversation strictly read-only, blocking all new comments, reactions, and automated comments. When unarchived, comments and reactions are re-enabled, but the pull request itself is not reopened. Archived pull requests are also hidden from public view, accessible only by repository administrators.

Why does it matter to an everyday developer?

This update allows teams that delegate moderation to users with the triage role to efficiently manage pull request queues, addressing spam, duplicates, or abandoned requests without relying on administrators. The stricter read-only behavior for archived pull requests also enhances project hygiene and reduces unintended activity on closed discussions.

What can the developer do now?

If you have triage or higher permissions on a repository, you can now archive and unarchive pull requests as part of routine moderation. Use this feature to keep your pull request backlog organized and to enforce stricter limits on participation in archived discussions. Repository owners can safely delegate this responsibility to trusted contributors without giving them write or admin access.