Request token for nodejs/userland-migrations#1055
Request token for nodejs/userland-migrations#1055avivkeller wants to merge 1 commit intonodejs:mainfrom
nodejs/userland-migrations#1055Conversation
There was a problem hiding this comment.
Pull request overview
Adds a new registry entry documenting a requested fine-grained @nodejs-github-bot token to support automation related to nodejs/userland-migrations.
Changes:
- Adds a new token registry row for
nodejs/userland-migrationswith secret nameLEARN_REPO_TOKEN - Adds the link reference for
nodejs/userland-migrations
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| [`nodejs-private/security-release`][] | `SECURITY_WG_GITHUB_TOKEN` | 2027-01-30 | <https://github.com/nodejs/admin/pull/950> | | ||
| [`nodejs/require-in-the-middle`][] | `RELEASE_PLEASE_GITHUB_TOKEN` | 2027-01-30 | <https://github.com/nodejs/admin/pull/951> | | ||
| [`nodejs/orchestrion-js`][] | `RELEASE_PLEASE_GITHUB_TOKEN` | 2026-11-08 | <https://github.com/nodejs/admin/pull/1023> | | ||
| [`nodejs/userland-migrations`][] | `LEARN_REPO_TOKEN` | | <https://github.com/nodejs/admin/pull/1055> | |
There was a problem hiding this comment.
The registry requires an expiration date (and notes tokens should be renewed within 1 year), but this new entry leaves the expiration date blank. Please set a concrete expiration date for this token so audits/renewals are trackable.
| [`nodejs/userland-migrations`][] | `LEARN_REPO_TOKEN` | | <https://github.com/nodejs/admin/pull/1055> | | |
| [`nodejs/userland-migrations`][] | `LEARN_REPO_TOKEN` | 2027-04-06 | <https://github.com/nodejs/admin/pull/1055> | |
| [`nodejs-private/security-release`][] | `SECURITY_WG_GITHUB_TOKEN` | 2027-01-30 | <https://github.com/nodejs/admin/pull/950> | | ||
| [`nodejs/require-in-the-middle`][] | `RELEASE_PLEASE_GITHUB_TOKEN` | 2027-01-30 | <https://github.com/nodejs/admin/pull/951> | | ||
| [`nodejs/orchestrion-js`][] | `RELEASE_PLEASE_GITHUB_TOKEN` | 2026-11-08 | <https://github.com/nodejs/admin/pull/1023> | | ||
| [`nodejs/userland-migrations`][] | `LEARN_REPO_TOKEN` | | <https://github.com/nodejs/admin/pull/1055> | |
There was a problem hiding this comment.
PR description says the token needs contents: write and pull-requests: write on nodejs/learn, but the registry entry adds nodejs/userland-migrations as the repo. If the token is actually scoped to nodejs/learn, the registry should list nodejs/learn (or otherwise clarify in the registry/PR description which repo the token is scoped to vs where the secret is stored).
Requesting a token with
contents: writeandpull-requests: writepermissions tonodejs/learnfornodejs/userland-migrations.Ref: nodejs/userland-migrations#423
cc @nodejs/web-infra @nodejs/userland-migrations @nodejs/TSC