I was trying to set up SourceTree to use GPG key signing for commits. I'm on a Mac (OS 10.13.3)
I have created keys and everything configured correctly. I can successfully commit/push stuff to a remote repo from the command line.
When I do a "gpg --list-key", in the terminal, the key shows up correctly
So then I tried do set up SourceTree and running into an issue. I've set the location of GPG in the SourceTree preferences and I am able to select the "Enable GPG key for signing commits. It automatically found my key, however, the user name that is showing up is "0", which is incorrect. The key that shows up is correct, however.
Why is it not showing the correct user? I only have one key generated and the user name does not match.
Obviously when I try to commit, I get an error:
error: gpg failed to sign the data
fatal: failed to write commit object
Anyone have any ideas?
@bganninAny chance you could help me? submitted a ticket, but can't seem to find the ticket I submitted. I just wanted to follow up on it and find out if there's a workaround, or if there's plans to fix (if this is a bug and not user error). I can no longer use SourceTree since the repos I'm trying to commit to require GPG signing.
The original ticket was SRCTREE-5407. Not sure if it was moved, permissions changes, or it was deleted.
Just looking for an update on the issue and hoping I can start using SourceTree again. =)
A vulnerability has been published today in regards to Sourcetree for Windows. The goal of this article is to give you a summary of information we have gathered from Atlassian Community as a st...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event