Skip to content

Commit d0421c9

Browse files
authored
Authentic Contributions: Persistent Commit Verification [GA] (#53499)
1 parent f53f320 commit d0421c9

File tree

3 files changed

+11
-5
lines changed

3 files changed

+11
-5
lines changed
Loading

content/authentication/managing-commit-signature-verification/adding-a-gpg-key-to-your-github-account.md

+4-5
Original file line numberDiff line numberDiff line change
@@ -24,13 +24,12 @@ shortTitle: Add a GPG key
2424

2525
To sign commits associated with your account on {% data variables.product.product_name %}, you can add a public GPG key to your personal account. Before you add a key, you should check for existing keys. If you don't find any existing keys, you can generate and copy a new key. For more information, see "[AUTOTITLE](/authentication/managing-commit-signature-verification/checking-for-existing-gpg-keys)" and "[AUTOTITLE](/authentication/managing-commit-signature-verification/generating-a-new-gpg-key)."
2626

27-
You can add multiple public keys to your account on {% data variables.product.product_name %}. Commits signed by any of the corresponding private keys will show as verified. If you remove a public key, any commits signed by the corresponding private key will no longer show as verified.
27+
You can add multiple public keys to your account on {% data variables.product.product_name %}. Commits signed by any of the corresponding private keys will show as verified. {% ifversion persistent-commit-verification %}Once a commit has been verified, any commits signed by the corresponding private key will continue to show as verified, even if the public key is removed.{% else %}If you remove a public key, any commits signed by the corresponding private key will no longer show as verified.{% endif %}
2828

29-
{% ifversion upload-expired-or-revoked-gpg-key %}
30-
To verify as many of your commits as possible, you can add expired and revoked keys. If the key meets all other verification requirements, commits that were previously signed by any of the corresponding private keys will show as verified and indicate that their signing key is expired or revoked.
29+
![Screenshot of a list of commits. One commit is marked with a "Verified" label. Next to the label, a dropdown explains that the commit was signed and shows a timestamp of when it was signed.](/assets/images/help/settings/verified-persistent-commit.png)
3130

32-
![Screenshot of a list of commits. One commit is marked with a "Verified" label. Below the label, a dropdown explains that the commit was signed, but the key has now expired.](/assets/images/help/settings/gpg-verified-with-expired-key.png)
33-
{% endif %}
31+
{% ifversion upload-expired-or-revoked-gpg-key %}
32+
To verify as many of your commits as possible, you can add expired and revoked keys. If the key meets all other verification requirements, commits that were previously signed by any of the corresponding private keys will show as verified and indicate that their signing key is expired or revoked.{% endif %}
3433

3534
{% data reusables.gpg.supported-gpg-key-algorithms %}
3635

Original file line numberDiff line numberDiff line change
@@ -0,0 +1,7 @@
1+
# Issue: 15674
2+
# Description: Once a commit signature is verified, it remains verified within its repository's network
3+
# Usage: {% ifversion persistent-commit-verification %} ... {% endif %}
4+
versions:
5+
fpt: '*'
6+
ghec: '*'
7+
ghes: '>=3.17'

0 commit comments

Comments
 (0)