Onboarding sxa as a releaser
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 4.4k
- Forks
- 675
- Avg merge
- 22h 29m
- Merged PRs (30d)
- 1
Description
@sxa has prepared two releases (https://github.com/nodejs/node/pull/42254, https://github.com/nodejs/node/pull/42285) 🎉
We now need to complete the remaining onboarding actions (from GOVERNANCE.md):
- Be added to the GitHub releasers team in the Node.js org (grants ci-release access)
- Be added to the GitHub security-release team in the Node.js and nodejs-private orgs
- Have a single, high quality SSH key added to the "dist" user on the primary www server
- Have a GPG key added to the nodejs/node README.md - https://github.com/nodejs/node/pull/64193
- The key should be cherry-picked to all active release branches.
- Open a PR in nodejs/docker-node to add gpg key to node.keys https://github.com/nodejs/docker-node/pull/2551
- Add the key to https://github.com/nodejs/release-keys https://github.com/nodejs/release-keys/pull/52
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 the adding-new-releasers section of GOVERNANCE.md and verify the linked GitHub team, key, and pull request records. The issue's checklist shows every onboarding action checked, so completion would require confirming those records and identifying any remaining action.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github
- Domain
- release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100