Aug 22, 2026
How to Set Up Verified GPG Commit Signing on GitHub
A verified badge builds trust in your commits. Setting it up takes just a few terminal commands:
Generate a key: Run gpg --full-generate-key, select RSA (4096 bits), set it to never expire, and use your exact GitHub name and email.
Export your public key: Run gpg --list-secret-keys --keyid-format=long to grab your Key ID, then export it using gpg --armor --export YOUR_KEY_ID.
Add it to GitHub: Go to GitHub Settings > SSH and GPG keys > New GPG key, and paste your exported block.
Enable auto-signing in Git: Run git config --global user.signingkey YOUR_KEY_ID and git config --global commit.gpgsign true.
Once configured, every git push automatically signs your work, giving your repo an official green Verified stamp of authenticity.
OTHER POSTS
Use npm scripts to Simplify Daily Tasks
Running long terminal commands over and over? Automate them with simple npm scripts in your package.json.
Read more →Learn Faster with Browser DevTools Tricks
Your browser is more powerful than you think. Chrome/Edge/Firefox DevTools can save you tons of time debugging and experimenting directly in the browser.
Read more →Fix "Email in this signature doesn't match the committer email" on GitHub
Pushed a signed GPG commit only to get a warning that the signature is unverified because of an email mismatch? Here is how to sync your GPG identity with Git.
Read more →Save Time with Emmet in VS Code
Writing HTML feels slow? Emmet abbreviations in VS Code can generate entire structures in seconds.
Read more →