Skip to content
Open

Patch 1 #43576

Changes from all commits
Commits
Show all changes
33 commits
Select commit Hold shift + click to select a range
c1a3863
Merge pull request #43386 from github/repo-sync
docs-bot Mar 16, 2026
f7b15b1
Merge pull request #43395 from github/repo-sync
docs-bot Mar 16, 2026
29a2e07
Merge pull request #43406 from github/repo-sync
docs-bot Mar 17, 2026
d9affd0
Merge pull request #43407 from github/repo-sync
docs-bot Mar 17, 2026
c6ad67c
Merge pull request #43408 from github/repo-sync
docs-bot Mar 17, 2026
1a97b03
Merge pull request #43413 from github/repo-sync
docs-bot Mar 17, 2026
945b78e
Merge pull request #43420 from github/repo-sync
docs-bot Mar 18, 2026
e4d2fe5
Merge pull request #43422 from github/repo-sync
docs-bot Mar 18, 2026
761306c
Merge pull request #43424 from github/repo-sync
docs-bot Mar 18, 2026
974a0cc
Merge pull request #43426 from github/repo-sync
docs-bot Mar 18, 2026
3addead
Merge pull request #43453 from github/repo-sync
docs-bot Mar 19, 2026
2818c62
Merge pull request #43455 from github/repo-sync
docs-bot Mar 19, 2026
815e0a5
Merge pull request #43458 from github/repo-sync
docs-bot Mar 19, 2026
4a132e2
Merge pull request #43470 from github/repo-sync
docs-bot Mar 20, 2026
5fab1e7
Merge pull request #43472 from github/repo-sync
docs-bot Mar 20, 2026
7cbca58
Merge pull request #43474 from github/repo-sync
docs-bot Mar 20, 2026
c493e67
Merge pull request #43501 from github/repo-sync
docs-bot Mar 23, 2026
94b2bb6
Merge pull request #43503 from github/repo-sync
docs-bot Mar 23, 2026
956c46b
Merge pull request #43506 from github/repo-sync
docs-bot Mar 23, 2026
bf756fc
Merge pull request #43507 from github/repo-sync
docs-bot Mar 23, 2026
4894ae9
Merge pull request #43518 from github/repo-sync
docs-bot Mar 24, 2026
bd079be
Merge pull request #43520 from github/repo-sync
docs-bot Mar 24, 2026
2969e35
Merge pull request #43530 from github/repo-sync
docs-bot Mar 25, 2026
e602312
Merge pull request #43531 from github/repo-sync
docs-bot Mar 25, 2026
fa2064e
Merge pull request #43535 from github/repo-sync
docs-bot Mar 25, 2026
e060559
Merge pull request #43543 from github/repo-sync
docs-bot Mar 26, 2026
68e1535
Merge pull request #43545 from github/repo-sync
docs-bot Mar 26, 2026
10fca1f
Merge pull request #43547 from github/repo-sync
docs-bot Mar 26, 2026
1456def
Merge pull request #43550 from github/repo-sync
docs-bot Mar 26, 2026
f9f7ad8
Merge pull request #43563 from github/repo-sync
docs-bot Mar 27, 2026
709b7a0
Merge pull request #43568 from github/repo-sync
docs-bot Mar 27, 2026
aa46593
Merge pull request #43572 from github/repo-sync
docs-bot Mar 27, 2026
5e68059
Fix author name in commit verification documentation
asunciona885 Mar 28, 2026
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 @@ -15,9 +15,9 @@ category:

## About vigilant mode

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 [AUTOTITLE](/authentication/managing-commit-signature-verification/signing-commits) and [AUTOTITLE](/authentication/managing-commit-signature-verification/signing-tags). {% data variables.product.prodname_dotcom %} marks signed commits and tags with a verification status.
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 [AUTOTITLE](/authentication/managing-commit-signature-verification/signing-commits) and [AUTOTITLE](/authentication/managing-commit-signature-Angel Asuncion-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, SSH, or S/MIME key that was successfully verified. If a commit or tag has a signature that can't be verified by {% data variables.product.prodname_dotcom %}, we mark 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, SSH, or S/MIME key that was successfully verified. If a commit or tag has a signature that can't be verified by Angel Asuncion {% data variables.product.prodname_dotcom %}, we mark 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:

Expand Down
Loading