8

I am using GitKraken as my git client and it was always working fine, but for a few days I am getting the error fatal: bad boolean config value 'null' for 'commit.gpgsign' when I use any other git clients. I have tried cmd, vscode, PowerShell in vscode and Git GUI. I have also uninstalled the GitKraken and try, but I guess it somehow retains the settings. Have you ever experienced this issue?

Sibeesh Venu
  • 18,755
  • 12
  • 103
  • 140

1 Answers1

11

After scratching my head for a while, I found the solution for the same. You just have to go to your .gitconfig file in your user directory (C:\Users\SibeeshVenu) and remove the preceding settings.

[commit]
    gpgSign = null

In the end, this is how my .gitconfig looks like.

[user]
    email = myemail
    name = Sibeesh Venu
    signingKey = null
    password = mypassword
[core]
    longpaths = true
[gpg]
    program = null
[tag]
    forceSignAnnotated = null
[credential]
    helper = store
Sibeesh Venu
  • 18,755
  • 12
  • 103
  • 140
  • 2
    *All* of those `= null` entries appear damaged by some software (not sure what software). The `program` setting should be the path name of a program to run to invoke the GPG signer/checker; the `forceSignAnnotated` setting should be either `true` or `false`; and the `signingKey` should be absent, or set to some valid signing key (I'm not sure if this would be the key itself, or a path name, but `null` is definitely wrong). – torek Aug 12 '21 at 01:54