GitHub + KeySigner

Protect the maintainers who control repositories and verify the identity of people signing changes.

What to check first

Try a signed commit in a test repository and inspect its verification result. Separately check the organization's owner recovery and branch rules.

Choose a KeySigner setup

Setup guide What it does and what to keep available
Approve a Git commit on your phone →

Sign a commit with the registered key so reviewers can see which signature GitHub verified.

You need Computer tools and KeySigner on iPhone.

Keep available The prior Git signing settings. The guide includes a rollback command and a separate step to remove the test key from GitHub.

Test a time-based sign-in code →

Use KeySigner to generate the second-factor code for a GitHub account.

You need KeySigner on iPhone or Mac with Sign-in codes.

Keep available GitHub recovery codes in a secure place you can reach outside KeySigner and GitHub.

KeySigner setup requirements →

What it covers

A verified commit signature does not approve a merge or authorize a release.

Make an offline recovery plan →

Troubleshooting

Does GitHub show your test commit as Unverified?

Compare the credential used to sign the commit with the signing key registered to your GitHub account. For a GPG signature, also check the committer email against your verified account email.

Check GitHub status for reports on GitHub.com services by feature.

Find documentation and support →

Documentation and support

GitHub documentation

Check commit and tag signature verification
Troubleshoot a commit signature
Set up authenticator codes for GitHub

KeySigner setup help

Ask about this setup →