Yes, I use it all the time. We didn't require it at work, until one employee started signing their commits, and everyone else thought the "verified" badge for t

Yes, I use it all the time. We didn't require it at work, until one employee started signing their commits, and everyone else thought the "verified" badge for the commit on github looked cool, so everyone else started doing it. Now mostly everyone does it at work. After adding your public key to your github account, you can set git to sign your commits by default. You can do that in ~/.gitconfig (or /<repo>/.git/config for specific repos). [user] signingkey = DEADBEEF [commit] gpgsign = true Then when you commit, it will try to sign the commit. When you push the commit to github, it will automatically show up as "verified" in the commit history. https://git-scm.com/book/en/v2/Git-Tools-Signing-Your-Work https://git-scm.com/book/en/v2/Git-Tools-Signing-Your-Work https://help.github.com/articles/signing-commits/ https://help.github.com/articles/signing-commits/