Skip to content
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

✨ Add command for release signers to easily import keys #8

Merged
merged 3 commits into from
Jul 1, 2021

Conversation

canterberry
Copy link
Collaborator

@canterberry canterberry commented Jun 30, 2021

Supercedes #6.

This changeset introduces an "add" command that can be used by
the Node.js release signing team to add or update their own
release signing keys.

$ ./cli.sh add <signing-key-id>

For example: ./cli.sh add 4ED778F539E3634C779C87C6D7062848A1AB005C

After this command has been added, members of the release signing
team can create PRs to update their own keys as follows:

  1. Clone the latest default branch (e.g: master) and create a feature branch.
  2. For each release signing key you have used or intend to use: run ./cli.sh add <key-id> with the full key ID.
  3. Manually update README.md, as needed.
  4. Commit the result, push to the feature branch, and create a PR to have that merged into the default branch.

This changeset introduces an "add" command that can be used by
the Node.js release signing team to add or update their own
release signing keys.

```
$ ./cli.sh add <signing-key-id>
```

For example: `./cli.sh add 4ED778F539E3634C779C87C6D7062848A1AB005C`

After this command has been added, members of the release signing
team can create PRs to update their own keys as follows:

 1. Clone the latest default branch (e.g: `master`) and create a feature branch.
 2. For each release signing key you have used or intend to use: run `./cli.sh add <key-id>` with the full key ID.
 3. Manually update README.md, as needed.
 4. Commit the result, push to the feature branch, and create a PR to have that merged into the default branch.
Copy link
Member

@targos targos left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't know much about shell syntax, but behavior with my key seems good:

$ ./cli.sh add 8FCCA13FEF1D0C2E91008E09770F7A9A5AE15600
gpg: WARNING: unsafe permissions on homedir '/Users/targos/git/nodejs/release-keys/gpg'
gpg: key 770F7A9A5AE15600: "Michaël Zasso (Targos) <[email protected]>" not changed
gpg: Total number processed: 1
gpg:              unchanged: 1
keys.list <- 8FCCA13FEF1D0C2E91008E09770F7A9A5AE15600

@canterberry canterberry merged commit 085a84e into nodejs:master Jul 1, 2021
@targos targos removed their assignment Oct 31, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants