Migrate away from @nodejs-github-bot tokens.
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 202
- Forks
- 183
- Avg merge
- 2m
- Merged PRs (30d)
- 1
Description
I think we should stop creating PATs associated with @nodejs-github-bot, and instead rely on the more secure alternative: GitHub App Tokens.
I've created a basic GitHub app that can be transferred into the org to replace @nodejs-github-bot.
WDYT?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with issue #1074 and review the linked nodejs-gha GitHub App proposal. No files, tests, or entry points are identified, so first clarify the migration scope and required decisions; the work is done when the replacement for @nodejs-github-bot tokens is agreed and implemented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github
- Domain
- authentication, security
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100