From 7447884b2eaa1f94f376979a07683f42258c11e3 Mon Sep 17 00:00:00 2001 From: Hema Shushu Date: Tue, 10 Dec 2024 09:45:46 +0800 Subject: [PATCH] Update checking-for-existing-gpg-keys.md MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Add a workaround for the “No valid identities found in this GPG data” error. --- .../checking-for-existing-gpg-keys.md | 1 + 1 file changed, 1 insertion(+) diff --git a/content/authentication/managing-commit-signature-verification/checking-for-existing-gpg-keys.md b/content/authentication/managing-commit-signature-verification/checking-for-existing-gpg-keys.md index f4dfda8f456d..9c35cdf6b57c 100644 --- a/content/authentication/managing-commit-signature-verification/checking-for-existing-gpg-keys.md +++ b/content/authentication/managing-commit-signature-verification/checking-for-existing-gpg-keys.md @@ -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` You can then [add your GPG key to your GitHub account](/authentication/managing-commit-signature-verification/adding-a-gpg-key-to-your-github-account).