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

keys: add RafaelGSS key #16

Merged
merged 1 commit into from
Jun 16, 2022
Merged

Conversation

RafaelGSS
Copy link
Member

No description provided.

@RafaelGSS RafaelGSS force-pushed the doc/add-rafaelgss-key branch from 20c5d02 to 31b1c89 Compare May 23, 2022 14:54
Copy link
Member

@richardlau richardlau left a comment

Choose a reason for hiding this comment

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

There's a list in the README.md that should be updated, but neither this PR nor #15 updates the preloaded GPG keyring so we can update the README when we do that. We'll want to update the keyring after merging the two pull requests (as the keyring is a binary file so can't be automatically merged from two separate pull requests).

@RafaelGSS
Copy link
Member Author

There's a list in the README.md that should be updated, but neither this PR nor #15 updates the preloaded GPG keyring so we can update the README when we do that. We'll want to update the keyring after merging the two pull requests (as the keyring is a binary file so can't be automatically merged from two separate pull requests).

How can I do that? Can I merge this one then?

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