-
Notifications
You must be signed in to change notification settings - Fork 135
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
Update commit queue token permission #640
Comments
admin/GITHUB_ORG_MANAGEMENT_POLICY.md Lines 129 to 136 in 87bc406
Link to the CQ: https://github.com/nodejs/node/runs/4131235476?check_suite_focus=true The app being already in use, asking for a fast-tracking this request. Please 👍 this comment to approve. |
Why do we need |
I'm not sure we need it, I've added it because of this sentence in GH REST API docs:
It may or may not be necessary, but given the delay of 72 hours for the fast-tracked change to be approved, I thought adding it to the list would not hurt. We should try to only add
Maybe @mmarchini can help with that? |
/cc @nodejs/tsc |
Ping @nodejs/tsc |
I 👍'ed the fast-track request. Is there anything else TSC should be doing with this? |
I think two 👍🏻 are enough. Now the difficult part will be to find someone who can do the change. |
I think anyone that has access to the @nodejs-github-bot GitHub account should be able to do that – the README mentions a 1password account, probably the credentials are there (I don't have access to it AFAIK). Lines 48 to 50 in 87bc406
|
@nodejs/github-bot |
@aduh95 try again now? |
Just tried, and it works: https://github.com/nodejs/node/runs/4194822955?check_suite_focus=true 🎉 thanks a lot! |
I've been trying to update the CQ to make it able to "purple-merge" PRs with the CQ. Before that, the CQ was using two tokens:
@nodejs/collaborators
)GITHUB_TOKEN
provided by @github-actions to comment/close on PRsGITHUB_TOKEN
is not allowed to merge PRs because it's not part of@nodejs/collaborators
, so @targos tried to use @nodejs-github-bot's token to run the CQ. Unfortunately this didn't work:https://github.com/nodejs/node/runs/4131235476?check_suite_focus=true
Originally posted by @aduh95 in nodejs/node#40742 (comment)
I'm asking for permission to update the permissions to make the Commit Queue work correctly:
read:org
notifications
For info, the current permissions for this token are
['read:user', 'repo', 'user:email', 'workflow']
.The text was updated successfully, but these errors were encountered: