From 7447884b2eaa1f94f376979a07683f42258c11e3 Mon Sep 17 00:00:00 2001 From: Hema Shushu Date: Tue, 10 Dec 2024 09:45:46 +0800 Subject: [PATCH 1/5] 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). From 21df759f1a83499117d03d15b00b27996505b370 Mon Sep 17 00:00:00 2001 From: Alex Nguyen <150945400+nguyenalex836@users.noreply.github.com> Date: Tue, 11 Feb 2025 13:39:01 -0800 Subject: [PATCH 2/5] Update content/authentication/managing-commit-signature-verification/checking-for-existing-gpg-keys.md Co-authored-by: Ben Ahmady <32935794+subatoi@users.noreply.github.com> --- .../checking-for-existing-gpg-keys.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) 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 9c35cdf6b57c..531d1940e821 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,7 +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` + Consider exporting your keys with the option `--export-options export-minimal`, which can prevent misreading keys that contain deprecated fields. You can then [add your GPG key to your GitHub account](/authentication/managing-commit-signature-verification/adding-a-gpg-key-to-your-github-account). From c10502c1d268e2a2e7ae28a40abfab3f8982dceb Mon Sep 17 00:00:00 2001 From: Alex Nguyen <150945400+nguyenalex836@users.noreply.github.com> Date: Tue, 11 Feb 2025 13:43:37 -0800 Subject: [PATCH 3/5] Fix indentation in GPG key export section --- .../checking-for-existing-gpg-keys.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) 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 60383a8130e6..58a02921d493 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,7 +29,7 @@ shortTitle: Existing GPG keys $ gpg --armor --export 3AA5C34371567BD2 # Prints the GPG public key, in ASCII armor format ``` - Consider exporting your keys with the option `--export-options export-minimal`, which can prevent misreading keys that contain deprecated fields. + Consider exporting your keys with the option `--export-options export-minimal`, which can prevent misreading keys that contain deprecated fields. You can then [add your GPG key to your GitHub account](/authentication/managing-commit-signature-verification/adding-a-gpg-key-to-your-github-account). From bdd0389e855e0b2d4b20420430cda4b1da6ffb47 Mon Sep 17 00:00:00 2001 From: Alex Nguyen <150945400+nguyenalex836@users.noreply.github.com> Date: Tue, 11 Feb 2025 14:20:45 -0800 Subject: [PATCH 4/5] Fix linter error --- .../checking-for-existing-gpg-keys.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) 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 58a02921d493..b4a5e455b322 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,7 +29,8 @@ shortTitle: Existing GPG keys $ gpg --armor --export 3AA5C34371567BD2 # Prints the GPG public key, in ASCII armor format ``` - Consider exporting your keys with the option `--export-options export-minimal`, which can prevent misreading keys that contain deprecated fields. + + Consider exporting your keys with the option `--export-options export-minimal`, which can prevent misreading keys that contain deprecated fields. You can then [add your GPG key to your GitHub account](/authentication/managing-commit-signature-verification/adding-a-gpg-key-to-your-github-account). From d02696a69934d3b4116084996c29abe209bb2f53 Mon Sep 17 00:00:00 2001 From: Alex Nguyen <150945400+nguyenalex836@users.noreply.github.com> Date: Tue, 11 Feb 2025 14:23:25 -0800 Subject: [PATCH 5/5] Fix linter error --- .../checking-for-existing-gpg-keys.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) 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 b4a5e455b322..20792d3a25e5 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,7 +29,7 @@ shortTitle: Existing GPG keys $ gpg --armor --export 3AA5C34371567BD2 # Prints the GPG public key, in ASCII armor format ``` - + Consider exporting your keys with the option `--export-options export-minimal`, which can prevent misreading keys that contain deprecated fields. You can then [add your GPG key to your GitHub account](/authentication/managing-commit-signature-verification/adding-a-gpg-key-to-your-github-account).