What are the correct role names for repository access, and what permissions do they confer?

[jkodroff]

Select Topic Area

Question

Body

The docs for resources like github_team_repository in the GH Terraform provider,, the GH user docs, and the GH API docs seem inconsistent with what the available roles are and what permissions they confer.

The github_team_repository docs say:

`permission` - (Optional) The permissions of team members regarding the repository.
  Must be one of `pull`, `triage`, `push`, `maintain`, `admin` or the name of an existing [custom repository role](https://docs.github.com/en/enterprise-cloud@latest/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization) within the organisation. Defaults to `pull`.

The Collaborators API docs say:

Checks the repository permission of a collaborator. The possible repository permissions are admin, write, read, and none.

Note: The permission attribute provides the legacy base roles of admin, write, read, and none, where the maintain role is mapped to write and the triage role is mapped to read. To determine the role assigned to the collaborator, see the role_name attribute, which will provide the full role name, including custom roles. The permissions hash can also be used to determine which base level of access the collaborator has to the repository.

According to Repository roles in GH docs, Read and Triage are not the same (they have different checkmarks in the screenshot below):

Can we get a single source of truth that is complete and accurate? (Even if these don't all actually point to the same value, there should be a single doc that explains all of this.)

[github-actions[bot]]

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬

[jkodroff]

This isn't resolved yet and needs some information from a GitHubber to clarify.

[acuteaura]

I'd love an answer here - the teams repository list REST API role_name attribute returns write after setting permissions to pull. This is not great.