Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Git command fails in some environment when fetching required information #74

Open
wdhongtw opened this issue Jan 9, 2025 · 2 comments
Labels
bug Something isn't working

Comments

@wdhongtw
Copy link
Owner

wdhongtw commented Jan 9, 2025

image

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.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

@wdhongtw wdhongtw added the bug Something isn't working label Jan 9, 2025
@AnnAngela
Copy link
Contributor

In WSL, you memory is correct:
image

Since I don't write code in Windows env, I cannot verify this behavior in Windows.

@AnnAngela
Copy link
Contributor

And the manual support your memory: https://git-scm.com/docs/git-config#FILES

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants