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

Update checking-for-existing-gpg-keys.md #35597

Merged
merged 6 commits into from
Feb 11, 2025
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -29,6 +29,7 @@ shortTitle: Existing GPG keys
$ gpg --armor --export 3AA5C34371567BD2
# Prints the GPG public key, in ASCII armor format
```
> If you encounter "No valid identities found in this GPG data" error, it may be because the public key you exported is too large or contains useless information, please add GPG option `--export-options export-minimal` to export again, e.g.: `$ gpg --armor --export-options export-minimal --export 3AA5C34371567BD2`
nguyenalex836 marked this conversation as resolved.
Show resolved Hide resolved

You can then [add your GPG key to your GitHub account](/authentication/managing-commit-signature-verification/adding-a-gpg-key-to-your-github-account).

Expand Down
Loading