We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
As per https://docs.github.com/en/rest/reference/teams#add-or-update-team-repository-permissions - custom role names (https://docs.github.com/en/enterprise-cloud@latest/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization) are now permitted when adding/updating permissions for teams.
The Terraform provider still only expects pull, triage, push, maintain, or admin
For the avoidance of doubt, I have tested setting permissions with a custom role name (it seems to be case sensitive) via the GH API and it works.
Would someone be so kind as to allow string values for the permission argument please?
The text was updated successfully, but these errors were encountered:
I raised a PR here, based on another - could anyone help in getting this reviewed/merged? 😃
#1113
Sorry, something went wrong.
@kfcampbell could we merge/release this?
Both of the linked PRs are ready to go (sorry about the delay in updating mine @joshuahancox)
Successfully merging a pull request may close this issue.
As per https://docs.github.com/en/rest/reference/teams#add-or-update-team-repository-permissions - custom role names (https://docs.github.com/en/enterprise-cloud@latest/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization) are now permitted when adding/updating permissions for teams.
The Terraform provider still only expects pull, triage, push, maintain, or admin
For the avoidance of doubt, I have tested setting permissions with a custom role name (it seems to be case sensitive) via the GH API and it works.
Would someone be so kind as to allow string values for the permission argument please?
The text was updated successfully, but these errors were encountered: