Uh oh!
There was an error while loading. Please reload this page.
doc: request token for wiby - #986
Conversation
bjohansebas
commented
Jul 19, 2025
cc: @nodejs/tsc |
legendecas
left a comment
There was a problem hiding this comment.
The requirement for requesting token via this method is limited to https://github.com/nodejs repositories.
Would you mind elaborating on why @nodejs-bot is needed in this process?
bjohansebas
commented
Jul 25, 2025
@legendecas we don't actually need @nodejs-bot. As I mentioned, the bot that has access to those repositories is @wiby-bot, so that's the one that can generate the tokens I need. I'm requesting this because someone with access to the @wiby-bot account posted this comment, so I assume the process needs to be handled here. The reason I need these tokens is because that's how the wiby package currently works, the tokens are used to create branches in those repositories and to read the status of commits. They're essential for getting all the tests in the repo to pass. Right now, I can't test that functionality, so every time I make changes, I have no way to know if I'm breaking the integration or not. Without those tokens, the tests fail, and that has blocked me from continuing to maintain the package. |
bjohansebas
commented
Jul 30, 2025
@nodejs/tsc, any way to unblock this? |
bjohansebas
commented
Aug 15, 2025
Hey, @nodejs/tsc, could you please review it? |
legendecas
commented
Aug 17, 2025
I think the questions still remain:
This is out of scope of the management of nodejs admin. @nodejs/package-maintenance @mhdawson@dominykas I'd appreciate if you could chime in to help moving this forward. FWIW, the current @wiby-bot account owners are https://github.com/nodejs/email/blob/02aa2cdad44a66c18529fd87dd80ebe7210585c7/iojs.org/aliases.json#L191-L197 |
Hey @nodejs/tsc, we can also store the token info in the package-maintenance repository, and have the group manage it, since technically this package is part of pkgjs and therefore under the working group’s direction |
@legendecas I can keep a record of what the token needs in the package-maintenance repository, since that group is the one delegated to maintain the package anyway. I just need access to 1Password to be able to do that #1031 and nodejs/email#288. |
Should fixnodejs/package-maintenance#629
This token should have push access to the following repositories:
The bot that has access to this is called @wiby-bot, and the access credentials are in Node.js's 1Password.