Custom role permissions for secrets and envs?

[fishpen0]

Select Topic Area

Product Feedback

Body

How do I give devs access to manage github actions secrets and environments without making them a respository admin? I am aware of custom roles, but looking through the role settings, envs and secrets appear to not be mapped to any permissions available to select from?

Also, there is still a mismatch between UI access and API access for some of these permissions, for example github/docs#1087 is still an issue

[xv-carlos-c]

2 years after and this is still not possible

[mijdavis2]

User's with write and maintain having the ability to create, update, and delete repo secrets via the API but NOT in the UI is extremely confusing and forces us to give full admin permissions for those that need to use the console instead of the api, which gives them undesired permissions as well. Please make this permission available in custom roles or make the UI perms consistent with the API perms.

This is incredibly unexpected and undesirable

[rajbos]

For people stumbling upon this, I documented things here: https://devopsjournal.io/blog/2022/11/02/GitHub-secrets-without-admin-rights

[mijdavis2]

This is clearly an AI spam response, WTH?! This was not helpful at all as all your points are completely invalid for this use case.