I followed few articles over the [pretty][1] attributes on [Git 2.10][2] release note. Going through which upgraded the git to 2.10.0 and made changes to global `.gitconfig` resulting as follows - 

    [filter &quot;lfs&quot;]
    	clean = git-lfs clean %f
    	smudge = git-lfs smudge %f
    	required = true
    [user]
    	name = xyz
    	email = abc.def@gmail.com
    	signingkey = AAAAAAA
    [core]
        excludesfile = /Users/xyz/.gitignore_global
    	editor = &#39;subl&#39; --wait
    [difftool &quot;sourcetree&quot;]
    	cmd = opendiff \&quot;$LOCAL\&quot; \&quot;$REMOTE\&quot;
    	path = 
    [mergetool &quot;sourcetree&quot;]
    	cmd = /Applications/SourceTree.app/Contents/Resources/opendiff-w.sh \&quot;$LOCAL\&quot; \&quot;$REMOTE\&quot; -ancestor \&quot;$BASE\&quot; -merge \&quot;$MERGED\&quot;
    	trustExitCode = true
    [alias]
    	lg = log --graph --pretty=format:&#39;%Cred%h%Creset -%C(yellow)%d%Creset %s %Cgreen(%cr) %C(bold blue)&lt;%an&gt;%Creset&#39; --abbrev-commit --date=relative
    [color &quot;diff&quot;]
    	old = red strike
    	new = green italic



But now that I try to sign my commits using 

    git commit -a -S -m &quot;message&quot;

I get to see the following error - 

&gt; You need a passphrase to unlock the secret key for 

&gt; user: &quot;XYZ (Digitally Signed) &lt;abc.def@gmail.com&gt;&quot; 

&gt; 2048-bit RSA key, ID AAAAAAAA, created 2016-07-01
&gt; 
&gt; error: gpg failed to sign the data fatal: failed to write commit
&gt; object


***Note*** - I can still commit changes using `git commit -a -m &quot;message&quot;`

***Is there a way to overcome the same? Or any change required in `gpg` configs to get along with the upgradation of git?***


----------


***Update 1***

Also seeking further usefulness, following https://stackoverflow.com/questions/10161198/is-there-a-way-to-autosign-commits-in-git-with-a-gpg-key. I&#39;ve already configured the key using 

    git config --global user.signingkey ED5CDE14(with my key) 
    git config --global commit.gpgsign true

and quite obviously getting the same error anyway.


  [1]: https://coderwall.com/p/euwpig/a-better-git-log
  [2]: https://github.com/blog/2242-git-2-10-has-been-released


All Gpg Signature Solutions on Gang of Coders

Total of 1 Gpg Signature Solutions

gpg failed to sign the data fatal: failed to write commit object [Git 2.10.0]