GitHub Triage role bypasses issue creation restrictions
GitHub's Triage role can now bypass issue creation restrictions, allowing these users to create issues even when creation is limited to collaborators. This enhancement helps teams maintain restricted issue creation while enabling triage users to contribute more effectively to repository maintenance. This change is now available for all repositories.
- →Triage role can bypass issue creation restrictions
- →Benefits of the Triage role update
Features (1) ›
- Triage role can bypass issue creation restrictions
Users with the Triage role can now create issues in repositories where issue creation is restricted to collaborators only. This change expands issue creation permissions to include trusted contributors with the triage role, in addition to those with write access.
Notes (1) ›
- Benefits of the Triage role update
This update enables teams to keep issue creation restricted while empowering triage-role users to more effectively support intake and repository maintenance. Feedback and questions can be shared in the Community discussion.
https://github.blog/changelog/2026-08-03-triage-role-can-bypass-issue-creation-restrictions
Related releases
- GitHub Copilot introduces Agent Plugins 1.0 for cross-client development GitHub Changelog ·
- GitHub Details Organization-Level Repository Rule Insights GitHub Changelog ·
- GitHub Enterprise Server 3.22 Release Candidate Now Available GitHub Changelog ·
- GitHub Copilot for JetBrains adds persistent memory, Ollama integration, and enterprise controls GitHub Changelog ·
- Automatically Migrate Branch Protection Rules to Repository Rulesets GitHub Changelog ·
- GitHub Copilot's MAI-Code-1-Flash model slated for deprecation GitHub Changelog ·