Administrators of organization-owned repositories can now assign “triage” and “maintain” roles to collaborators and teams.
It’s no surprise that we believe the best software is built together. Users open issues to report bugs or request new features, contributors discuss potential implementations, and maintainers review proposed changes. But as a project and its community grows, ensuring that feedback and decisions are addressed can often be a full-time job on top of the work you’re already doing.
Historically, repository permissions on GitHub were limited to read, write, and admin. The only way to grant additional permissions to individual teams or members was to provide them with full permissions to modify a project’s source code. At Satellite, we launched a public beta of our triage and maintain roles to empower administrators to delegate responsibilities to trusted members. Today, these roles are now generally available.
The triage role allows users to more proactively manage projects without the need for write access to the code. These users are able to open and close issues and pull requests, request reviews from developers, and manage project milestones.
The maintain role allows users to manage a repository without access to sensitive or potentially destructive actions. These users are able to create and edit releases, push to protected branches, lock conversations, and manage interaction limits.
These new roles are now available to all organizations on the Free, Team, and Enterprise Cloud plans. Organization and repository admins can apply the roles to teams and users in the Collaborators & teams tab of their repository settings page.
Start your free trial for 30 days and increase your team’s collaboration. $21 per user/month after trial expires.
Curious about other plans?
Learn how GitHub's Enterprise Cloud, GitHub Actions, and Arm's latest Automotive Enhanced processors, work together to usher in a new era of efficient, scalable, and flexible automotive software creation.
Say goodbye to constant mouse clicking and hello to seamless navigation with GitHub shortcuts.
In March, we experienced two incidents that resulted in degraded performance across GitHub services.
Jarryd McCree 
