-
Notifications
You must be signed in to change notification settings - Fork 93
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
[BUG] - Contributor workflow comment trigger does not work properly #1769
Comments
There is this discussion https://github.com/orgs/community/discussions/18690 where people seem to have the same issue. @aktech Do you have any additional insights on this since your comment? |
Hey @pmeier (and @iameskild) you'd need to change your Organisation visibility to Public, for it to identify both of you as Here is mine: |
I don't see any such option in my personal settings. Are you sure that we have to do it on our side or does this happen on the organization level by an admin? If we need to do it, could you post minimal step-by-step instructions on how to get there? |
You can change the toggle here (next to your username): https://github.com/orgs/nebari-dev/people |
That works, thanks! |
Describe the bug
By commenting
/bot run tests
as a maintainer on a PR, we should be able to trigger some workflows that are usually not run for regular contributors. This is done through this workflownebari/.github/workflows/contributor.yaml
Lines 1 to 5 in 6b38c8c
The trigger works fine until it comes to checking the permissions of the user sending the comment. We currently check for these roles
nebari/.github/workflows/contributor.yaml
Line 31 in 6b38c8c
They are correct according to the documentation:
However, I and @iameskild as well, are listed as
CONTRIBUTOR
, although we should haveMAINTAINER
permissions.Expected behavior
Being able to trigger contributor tests as maintainer.
OS and architecture in which you are running Nebari
GitHub repository
How to Reproduce the problem?
Comment
/bot run tests
on a PR, e.g. #1725. Curious to see what the bot spits out for people with elevated permissions.Command output
No response
Versions and dependencies used.
No response
Compute environment
None
Integrations
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: