Skip to content
New issue

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

user's permission level 'none' - moving from v1 to v3 #189

Closed
Babu458 opened this issue Feb 3, 2023 · 3 comments
Closed

user's permission level 'none' - moving from v1 to v3 #189

Babu458 opened this issue Feb 3, 2023 · 3 comments

Comments

@Babu458
Copy link

Babu458 commented Feb 3, 2023

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:

  • name: Slash Command Dispatch
    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
@peter-evans
Copy link
Owner

Hi @Babu458

Please see this issue: #128

The fix is that the PAT should be given the org:read scope.

@zliang-akamai
Copy link

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.

@peter-evans
Copy link
Owner

Hi @zliang-akamai

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants