Expanding REST API support for triage and maintain roles

We are expanding support for the triage and maintain permissions in the REST API. Users with the triage or maintain permissions can now use endpoints that reflect what they can do in a repository, such as adding a label to an issue. Additionally, these new permissions can now be granted and managed via the API and will show up as assigned roles in API responses.

For more information about these roles, see "Repository permission levels for an organization" in the GitHub Help documentation.

Endpoints you can access with the triage permission

• POST /repos/:owner/:repo/issues/:issue_number/labels
• DELETE /repos/:owner/:repo/issues/:issue_number/labels/:name
• POST /repos/:owner/:repo/issues/:issue_number/assignees
• DELETE /repos/:owner/:repo/issues/:issue_number/assignees
• POST /repos/:owner/:repo/pulls/:pull_number/requested_reviewers

Endpoints you can access with the maintain permission

• PUT /repos/:owner/:repo/topics
• PUT /repos/:owner/:repo/interaction-limits
• All of the endpoints that you can use with the triage permission role:
  • POST /repos/:owner/:repo/issues/:issue_number/labels
  • DELETE /repos/:owner/:repo/issues/:issue_number/labels/:name
  • POST /repos/:owner/:repo/issues/:issue_number/assignees
  • DELETE /repos/:owner/:repo/issues/:issue_number/assignees
  • POST /repos/:owner/:repo/pulls/:pull_number/requested_reviewers

Endpoints to assign, update, or view permissions

These endpoints will now work to manage the triage and maintain permissions.

• PUT /repos/:owner/:repo/collaborators/:username
• GET /repos/:owner/:repo/invitations
• PATCH /repos/:owner/:repo/invitations/:invitation_id
• GET /user/repository_invitations
• GET /orgs/:org/teams/:team_slug/repos/:owner/:repo
• PUT /orgs/:org/teams/:team_slug/repos/:owner/:repo
• GET /orgs/:org/teams/:team_slug/repos