You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Unlike user.signingKey, lacking of commit.gpgSign setting in local scope (current git repo) seems to
fail the git commit in some environment.
If my memory is correct, both commit.gpgSignuser.signingKey will fallback to global sertting (in user home folder)
when there is no such config in local scope.
My memory may be wrong. In that case, we should support "command-failure" as "falsy/empty" value when
reading / parsing git config output.
OS: Windows 11
Git: git version 2.45.2.vfs.0.2
The text was updated successfully, but these errors were encountered:
The files are read in the order given above, with last value found taking precedence over values read earlier. When multiple values are taken then all values of a key from all files will be used.
Unlike
user.signingKey
, lacking ofcommit.gpgSign
setting in local scope (current git repo) seems tofail the git commit in some environment.
If my memory is correct, both
commit.gpgSign
user.signingKey
will fallback to global sertting (in user home folder)when there is no such config in local scope.
My memory may be wrong. In that case, we should support "command-failure" as "falsy/empty" value when
reading / parsing git config output.
OS: Windows 11
Git: git version 2.45.2.vfs.0.2
The text was updated successfully, but these errors were encountered: