Triage role users or higher can now archive pull requests

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" "http://www.w3.org/TR/REC-html40/loose.dtd"> Users with the triage role or higher in a repository can now archive and unarchive pull requests. Previously, archiving was limited to repository administrators, requiring trusted triagers to hand routine moderation work to someone with higher permissions.

Maintainers increasingly rely on triagers to keep pull request queues healthy without granting them permission to change code. Archiving—often used for spam, duplicate, or abandoned pull requests—is a common moderation action, and restricting it to administrators created unnecessary friction for projects that delegate this work.

We’ve also improved how archived pull requests become read-only. Previously, archiving would lock the pull request, but admins were still able to leave comments. Now, we’re preventing any new activity on the pull request once it’s been archived. This keeps archived pull requests read-only without granting triage users the ability to manipulate a conversation’s locked state, which requires write access.

With these changes:

Users with the triage, write, maintain, or admin role can archive and unarchive pull requests.

Archiving automatically closes the pull request and makes its conversation read-only.

New comments, reactions, and automated comments are blocked while a pull request is archived.

Archived pull requests are hidden from public view and remain visible to repository administrators.

Unarchiving restores the ability to comment and react, but does not reopen the pull request.

If you have any questions or feedback, drop a comment in our Community discussion.

The post Triage role users or higher can now archive pull requests appeared first on The GitHub Blog.