-
Notifications
You must be signed in to change notification settings - Fork 1
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
Fix Git test when global gitconfig signs all commits #35
Conversation
I have git signing enabled in my environment, and I don't have issues. Can you describe what behavior this fixes? Is the issue that you're prompted to enter a password to unlock the signing key? I think it would be better for tests to run in isolation of the user's config, rather than piecemeal reset default configs. I remember doing this recently by monkeypatching the |
sorry for not responding for so long, I forgot about this. I don't know what's the difference between our setups, but on my machine the tests outright fail. My only guess is that the GPG key is not associated with the mock email address, that's why gpg refuses to sign immediately. Here is the test log for reference:
|
I also don't have a key for the "Important User". I only have a key for myself. And when I run the tests, the commits are signed by me (and not the committer). My guess is that your git config is more strict about what commits it will sign. I thought that the 2.3 release had fixed this issue, but I did some more investigation and it seems that my use of |
the new version fixed the problem, thanks! |
No description provided.