https://pantsbuild.org/ logo
Join Slack
Powered by
<https://twitter.com/mjg59/status/1486462124897361...
# random
b
e
h
Linus is such a sweetheart
c
But no sugar šŸ˜›
e
Well, it was a sweet prediction 10 years prior to the event. He directly addressed the bogus email issue!
āž• 1
h
He's usually right, just also a giant knob about it...
šŸ˜… 1
ā˜ļø 1
c
So in this vein, Iā€™ve now setup (again, apparently Iā€™ve done this in the past, just not enabled it in my git config globally) my git signing. So all commits from me are now signed. https://github.com/pantsbuild/pants/pull/14314/commits/27ffd9adfc3922d7a09260a0263494f211850f38
h
That's a good idea. Are there setup instructions to follow?
c
Yes, I googled ā€œgit sign commitā€ and used the top two results to setup. https://git-scm.com/book/en/v2/Git-Tools-Signing-Your-Work https://docs.github.com/en/authentication/managing-commit-signature-verification/signing-commits (and related pages under ā€œFurther Readingā€) Hereā€™s a brief transcript I used:
Copy code
gpg --full-generate-key
gpg --list-keys --keyid-format=long
gpg --armor --export <key id>  # For registration in your Github profile
git config --global user.signingkey <key id>  # optional if only a single key in your setup
git config --global commit.gpgsign true  # optional
gpg --send-keys <key id>  # optional, probably a good idea to enable peers to verify your commits
I also installed a recent version of https://gpgtools.org/ on my Mac.
Iā€™ll add to this too, that I changed the cache ttl for my signing key in 
gpg-agent
to more than the default 2 hours, by changing my 
~/.gnupg/gpg-agent.conf
to:
Copy code
# Set ttl to 400 days..
default-cache-ttl 34560000
max-cache-ttl 34560000
Primarily due to the git commit signing failing if the passphrase was not active in the agents cache, for unknown reasons.
2 Views
Open in Slack
PreviousNext
Powered by