3 ms·

GitHub Desktop doesn't support commit/tag signing at this point. Sorry.

wilg 10y ago
Drat!
mrsteveman1 10y ago
Hopefully will at some point, it's one of the few reasons I use SourceTree at the moment. GPG in Github Desktop would be a fantastic addition :)
- alain_gilbert 10y ago
  Do you use the "git flow" feature of SourceTree ? I have a hard time trying to sign my merge commit. (after a new release for example) I wonder if you were able to do it ?
  - mrsteveman1 10y ago
    Nope no git flow here sorry :) Is it failing to give you the option to sign (UI bug)?
    - alain_gilbert 10y ago
      There 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 10y 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 10y ago
        For 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 10y ago
        It looks like adding the no-tty in gpg.conf fixed it :D Thank you !
        standardhuman 10y ago
        No problem. :) I'm glad it worked out for you!

wilg 10y ago

Drat!

Hopefully will at some point, it's one of the few reasons I use SourceTree at the moment. GPG in Github Desktop would be a fantastic addition :)

alain_gilbert 10y ago
Do you use the "git flow" feature of SourceTree ? I have a hard time trying to sign my merge commit. (after a new release for example) I wonder if you were able to do it ?
- mrsteveman1 10y ago
  Nope no git flow here sorry :) Is it failing to give you the option to sign (UI bug)?
  - alain_gilbert 10y ago
    There 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 10y 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 10y ago
      For 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 10y ago
        It looks like adding the no-tty in gpg.conf fixed it :D Thank you !
        standardhuman 10y ago
        No problem. :) I'm glad it worked out for you!