94

Trying to commit my changes by using GitHub Desktop and getting this:

enter image description here

error: cannot run gpg: No such file or directory

error: could not run gpg.

fatal: failed to write commit object (128)

Firstly that not worked for terminal too and i create gpg-key and plugged in to my GitHub Account Now it's working well in Terminal but Desktop version still not working.

In Oficial doccumentation for GitHub Desktop i found some notation:

Note: GitHub Desktop does not support GPG signing.

Community
  • 1
  • 1
Ilia Rebane
  • 1,251
  • 1
  • 9
  • 10

4 Answers4

228

Solved it.

So as GitHub Desktop was complaining about not being able to find gpg (I had installed it via homebrew), I figured there should be a way to tell git the exact path of gpg, turns out there is:

gpg.program Use this custom program instead of "gpg" found on $PATH when making or verifying a PGP signature. The program must support the same command-line interface as GPG, namely, to verify a detached signature, "gpg --verify $file - <$signature" is run, and the program is expected to signal a good signature by exiting with code 0, and to generate an ASCII-armored detached signature, the standard input of "gpg -bsau $key" is fed with the contents to be signed, and the program is expected to send the result to its standard output. https://git-scm.com/docs/git-config

So running the following solved the problem:

git config --global gpg.program "$(which gpg)"

GitHub got back to me and said that some users also need to use:

echo "no-tty" >> ~/.gnupg/gpg.conf
balupton
  • 47,113
  • 32
  • 131
  • 182
13

It has something to do with commit signing (https://help.github.com/en/articles/signing-commits).

In case you use Github Desktop (which doesn't support commit signing as highlighted right at the beginning of the article linked above) or if you don't need commit signing (or don't even know what it is), one thing you can do is to disable gpg commit signing by running a command like git config --global commit.gpgsign false or edit your .git/config file manually:

[commit]
  # https://help.github.com/articles/signing-commits-using-gpg/
  gpgsign = false

Hope it helps someone.

Heitor Althmann
  • 307
  • 2
  • 5
12

For Mac and gpg2 installed

git config --global gpg.program $(which gpg2)

This works for me.

And after above command, your .gitconfig should look like below

[user]
    email = yogesh.jadhav@xxx.com.au
    name = jadhavy
    signingkey = xxx
[credential]
    helper = osxkeychain
[gpg]
    program = /usr/local/MacGPG2/bin/gpg2
[commit]
    gpgsign = true
[core]
    autocrlf = input
ynerdy
  • 564
  • 4
  • 7
4

SOLUTION FOR VSCODE USERS:

Under settings search for GPG and uncheck it:

VS CODE IMAGE

Now, why would you uncheck it?

You only need this extension if using the Gnu Privacy Guard. If you don't know what it is, then you definitely do not need to worry about it.

However, just in case you want to know what is going on check out: https://www.gnupg.org/

victorkolis
  • 780
  • 13
  • 13