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
This action is not dispatching the commands and through this message " Command 'ok-to-apply-dev' is not configured for the user's permission level 'none' ". We have upgraded the from v1 to v3 and the permissions didn't change. The requester has admin access to the repo before and after the upgrade.
Hi @peter-evans
I am wondering why it needs org:read permission, and would it be possible to still dispatch the command when org:read is not granted? I think it would be nicer to let it skip the accessing repository collaborators step when it can't access it.
Please see #128 for why org:read is necessary. GitHub changed the permissions model to require that scope in order to read the permissions of org users. If the action cannot determine the user's permission then it will default to none. So you can use the action without org:read, it just means that you have to set the permission of the command to none so that any user can execute it.
This action is not dispatching the commands and through this message " Command 'ok-to-apply-dev' is not configured for the user's permission level 'none' ". We have upgraded the from v1 to v3 and the permissions didn't change. The requester has admin access to the repo before and after the upgrade.
current config:
uses: peter-evans/slash-command-dispatch@v3
env:
TOKEN: ***
with:
token: ***
reaction-token: ***
issue-type: pull-request
commands: ok-to-apply-dev
static-args: sha
permission: write
The text was updated successfully, but these errors were encountered: