Update displaying-verification-statuses-for-all-of-your-commits.md

x10an14 · web-flow · commit 0386503e9377 · 2021-07-13T18:02:52.000+02:00
It says cryptographically unverified, when it in fact _is_ cryptographically verified.

I'd suggest Github changes this scenario to `partially verified` at the very least (as opposed to "WARNING! WARNING! UNVERIFIED!", but ideally I'd like to be allowed to set whatever author email I want in my git commits, without that impeding on the veracity of my GPG signatures.

My use-case is to not spread an email I care about more than I have to. Enough trawlers already - few if any care to parse GPG keys and extract (it seems).
9/10 times (in my personal experience) they just trawl github commit logs with a webscraping service instead.

Those who think that they must match (that the git commit/tag author email gives any security at all) have a nasty surprise-in-waiting.
diff --git a/content/github/authenticating-to-github/managing-commit-signature-verification/displaying-verification-statuses-for-all-of-your-commits.md b/content/github/authenticating-to-github/managing-commit-signature-verification/displaying-verification-statuses-for-all-of-your-commits.md
@@ -16,15 +16,15 @@ redirect_from:
 
 When you work locally on your computer, Git allows you to set the author of your changes and the identity of the committer. This, potentially, makes it difficult for other people to be confident that commits and tags you create were actually created by you. To help solve this problem you can sign your commits and tags. For more information, see "[Signing commits](/github/authenticating-to-github/signing-commits)" and "[Signing tags](/github/authenticating-to-github/signing-tags)." {% data variables.product.prodname_dotcom %} marks signed commits and tags with a verification status. 
 
-By default commits and tags are marked "Verified" if they are signed with a GPG or S/MIME key that was successfully verified. If a commit or tag has a signature that can't be verified, {% data variables.product.prodname_dotcom %} marks the commit or tag "Unverified." In all other cases no verification status is displayed.
+By default commits and tags are marked "Verified" if they are signed with a GPG or S/MIME key that was successfully verified. If a commit or tag has a signature that can't be verified - or can be cryptographically verified but the GPG key's email doesn't match the commit's author email - then {% data variables.product.prodname_dotcom %} marks the commit or tag "Unverified." In all other cases no verification status is displayed.
 
 However, you can give other users increased confidence in the identity attributed to your commits and tags by enabling vigilant mode in your {% data variables.product.prodname_dotcom %} settings. With vigilant mode enabled, all of your commits and tags are marked with one of three verification statuses.
 
 ![Signature verification statuses](/assets/images/help/commits/signature-verification-statuses.png)
 
 {% data reusables.identity-and-permissions.vigilant-mode-verification-statuses %}
 
-You should only enable vigilant mode if you sign all of your commits and tags. After enabling this mode, any unsigned commits or tags that you generate locally and push to {% data variables.product.prodname_dotcom %} will be marked "Unverified."
+You should only enable vigilant mode if you sign all of your commits and tags, and ensure that you _always_ set git commit author email to an (identical) email listed on your GPG primary key when using Github. After enabling this mode, any unsigned commits or tags that you generate locally and push to {% data variables.product.prodname_dotcom %} will be marked "Unverified."
 
 {% data reusables.identity-and-permissions.verification-status-check %}
 
