Add "No secret key" solution to GitHub lesson (010)

[jcoliver]

From A. Leach:

I had to create a GPG key, configure it to be a signature, and then tell Github what it was — phew!

From the stack overflow you sent during the workshop, I then followed the steps outlined in these three sites:

• Install and create a gpg key: https://docs.github.com/en/authentication/managing-commit-signature-verification/generating-a-new-gpg-key (including downloading the gpg command tool Gpg4win)
• Set key as primary gpg signing key: https://docs.github.com/en/authentication/managing-commit-signature-verification/telling-git-about-your-signing-key
• Add the gpg key to github: https://docs.github.com/en/authentication/managing-commit-signature-verification/adding-a-gpg-key-to-your-github-account

After these steps, I was able to commit and push to the github repo that I created.