-
Notifications
You must be signed in to change notification settings - Fork 137
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
Create new github-bot personal token for nodejs/node-v8 automation #587
Comments
+1 |
2 similar comments
+1 |
+1 |
@nodejs/community-committee PTAL |
Ping |
Added to commcomm agenda as it needs one more approval from them |
Hi hello yes, +1 |
Hi. +1 from me too. |
Thank you! @mmarchini I think you're one of the few people who both have access to the github bot and repository settings? Would you be able to create the token and add it to https://github.com/nodejs/node-v8/settings/secrets/actions/new ? |
I don't know who else to ask 😕 |
@bnb I've not been in the loop of creating tokens in the past. I think @joyeecheung was involved in the github bot work. @joyeecheung do you know? |
I've added a CANARY_UPDATE token with the scopes mentioned in the OP, @targos can you try it out? |
BTW all I did was creating a personal access token and adding it to the repository, according to the documentation here https://docs.github.com/en/actions/reference/authentication-in-a-workflow |
Thank you @joyeecheung, it's working ! |
A token is needed with the
public_repo
andworkflow
scopes.This is for a daily workflow that will update the
node-v8
's canary branch with latest Node.js commit and V8 lkgr.workflow
is needed for cases where the Node.js update contains changes to.github/workflows
.Reference: nodejs/node-v8#171
/cc @nodejs/tsc @nodejs/community-committee
The text was updated successfully, but these errors were encountered: