4 ms·
Nope no git flow here sorry :) Is it failing to give you the option to sign (UI bug)?
by mrsteveman1 11y ago
Nope no git flow here sorry :)
Is it failing to give you the option to sign (UI bug)?
- alain_gilbert 11y agoThere is no UI that allows you to specify that you want the merge commit to be signed. And if you configure git to sign all commits, you get this error: https://confluence.atlassian.com/sourcetreekb/sourcetree-commits-fail-when-using-git-signed-commits-794199810.html https://confluence.atlassian.com/sourcetreekb/sourcetree-com...
- mrsteveman1 11y ago> There is no UI that allows you to specify that you want the merge commit to be signed. Ah ok, I see what you mean. I don't think theres a way to have rebase re-sign things inside SourceTree either, I run in to that one constantly and have to open a terminal.
- standardhuman 11y agoFor what it's worth, I had that same error message (OS X), and I managed to fix it. After using homebrew to make sure my git was up-to-date and gpg was also installed correctly, I told git where gpg is (for some reason, despite being in my PATH, it wasn't registering?): git config --global gpg.program /usr/local/bin/gpg After that, I had to make a tweak to gpg so I didn't get another annoying error. In ~/.gnupg/gpg.conf, adding 'no-tty' got everything working smoothly. I agree that that was way too tedious, but it did work out. :)
- alain_gilbert 11y agoIt looks like adding the no-tty in gpg.conf fixed it :D Thank you !
- standardhuman 11y agoNo problem. :) I'm glad it worked out for you!