GitHub has updated repository moderation permissions to allow users with the triage role or higher to archive and unarchive pull requests. The change expands administrative controls that were previously restricted strictly to repository administrators, granting triage, write, maintain, and admin roles authority over pull request archiving operations.
Reducing Moderation Friction in Open Source
Maintainers of open-source projects frequently rely on dedicated triage contributors to manage incoming submissions and organize issue queues without granting them permission to alter repository code. In many projects, handling routine moderation tasks—such as filing away spam, duplicate contributions, or abandoned pull requests—required escalating actions to administrators who held top-level permissions. Handing these low-level administrative duties to project leaders created operational friction. Permitting triage users to archive pull requests allows maintainers to delegate queue cleanup while keeping core codebase write permissions restricted.
Enforcing Read-Only State for Archived Content
Alongside expanded permissions, GitHub adjusted how archived pull requests handle ongoing activity. Previously, archiving locked a pull request thread while still permitting repository administrators to leave comments. Under the updated system, archiving a pull request automatically closes it and enforces a complete read-only restriction across all account levels, preventing triage users from needing write access to manipulate a conversation's locked status.
While a pull request remains archived, GitHub blocks all new activity, including manual comments, emoji reactions, and automated bot interactions. Archived pull requests are also removed from public view, remaining visible exclusively to repository administrators.
Restoring Interactive Features via Unarchiving
GitHub also defined specific behavior for restoring archived pull requests. When a user with sufficient permissions unarchives a pull request, interactive functions are restored, allowing contributors to comment and react on the thread once again. However, unarchiving does not automatically reopen the pull request; the submission remains closed until explicitly reopened through standard repository procedures.
AI-generated editorial illustration; not a documentary photograph.
Source: Triage role users or higher can now archive pull requests
SIGNAL TITANS
Leave a Reply