I've enabled GPG commit signing on the command line, and manually enabled via the "Repository Settings" section of SourceTree for each repo:
Screen Shot 2016-04-11 at 15.12.48.png
If I manually select "Sign commit" each time SourceTree correctly signs my commits:
Screen Shot 2016-04-11 at 15.16.48.png
However any other operation like stash or rebase doesn't seem to include the GPG options in the command and I get the following "gpg: cannot open `/dev/tty': Device not configured" error:
Screen Shot 2016-04-11 at 15.18.41.png
I see you even have a support article about this, but the proposed solution is enabling GPG signing in SourceTree which I've already done.
git config --global gpg.program gpg2
This maybe your answer.
thanks!!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
this did the trick for me, thanks!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Remove the gpgsign
attribute in the [commit]
section of your .gitconfig
if it's there.
This solved it for me.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I have to manually select "Sign Commit" in SourceTree anyways, even with the attribute enabled.
So I think it only takes effect for commits done via Terminal. Have you restarted SourceTree after modifying the config?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I have, and SourceTree doesn't respect this global git default. I'd rather not remove this since I want all commits to be signed - SourceTree should improve its GPG support.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Absolutely, it would make more sense for them to enhance the software to respect the standards.
Honestly, I've stopped using stashes because of this issue, which is really annoying :-/ The workaround I proposed above is NOT viable at all.
Please Atlassian, make SourceTree work better with GPG!
edit: Check this out, worked perfectly for me!
https://answers.atlassian.com/questions/38060409/answers/38398747
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I confirm that I am having same issue with rebasing.
+1
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I'm having the same issue.
Disabling the key signing for the repository also doesn't help, I can't stash anything any more!
Any news on this?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.