-
-
Notifications
You must be signed in to change notification settings - Fork 71
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
Build fails if git config log.showSignature true
#86
Comments
RussKie
added a commit
to gitextensions/gitextensions
that referenced
this issue
Dec 1, 2018
* Assume files in which we inject the build number as "unchanged" * Ensure no other files have changed * Mitigate build failures due to invalid gpg signatures, a workaround for devlooped/GitInfo#86 Closes #5698
RussKie
added a commit
to gitextensions/gitextensions
that referenced
this issue
Dec 1, 2018
* Assume files in which we inject the build number as "unchanged" * Ensure no other files have changed * Mitigate build failures due to invalid gpg signatures, a workaround for devlooped/GitInfo#86 Closes #5698
Or use:
|
Thanks for reporting and suggesting a clean fix! |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
All of a sudden my project failed to build with the following error:
Obviously when solution is compiled, GitInfo emits incorrect info.
\obj\Debug\GitInfo.cache:
Running the
git log
command in bash produces the following result:When
git config log.showSignature false
, the correct info is emitted:Expected:
I think you should set
git config log.showSignature false
(if it is set totrue
) when you're gathering information, and restore it back, when done.The text was updated successfully, but these errors were encountered: