You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, to generate a token that can create commit statuses via the API, it must have write:repository. This is less than ideal from a security perspective, where I'd like to give a token to some automation tools that can write commit statuses but not write to the repository.
Proposal: create a new permissions for commit statuses (read, and read+write) and update the API to only require commit statuses privileges to read/write commit status. Additionally, for backwards compatibility and sanity leave the repository permission as sufficient for commit statuses as well.
If this idea is acceptable, I'd be happy to implement it myself.
Screenshots
No response
The text was updated successfully, but these errors were encountered:
Feature Description
Currently, to generate a token that can create commit statuses via the API, it must have
write:repository
. This is less than ideal from a security perspective, where I'd like to give a token to some automation tools that can write commit statuses but not write to the repository.Proposal: create a new permissions for commit statuses (read, and read+write) and update the API to only require commit statuses privileges to read/write commit status. Additionally, for backwards compatibility and sanity leave the
repository
permission as sufficient for commit statuses as well.If this idea is acceptable, I'd be happy to implement it myself.
Screenshots
No response
The text was updated successfully, but these errors were encountered: