We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Describe the bug
Not sure if it's a bug or just my misinterpretation of the output, but the new jq has a "dirty" suffix, should that be the case?
jq
To Reproduce
Download the latest version of jq, then run:
$ jq-win64.exe --version
Produces:
jq-1.7-dirty
Expected behavior
That should probably just print jq-1.7.
jq-1.7
Environment (please complete the following information):
Additional context
I have noticed it when testing an update of the Chocolatey package that I maintain.
The text was updated successfully, but these errors were encountered:
Huh, yes, I see that, but I don't see what's different about the GitHub Actions CI workflow build for Linux vs. Windows that would cause this.
Sorry, something went wrong.
Disable core.autocrlf on Windows to prevent submodule diffs (fix jqla…
386c38e
…ng#2886)
Disable core.autocrlf on Windows to prevent submodule diffs (fix #2886)…
5ea1a4a
… (#2888)
Successfully merging a pull request may close this issue.
Describe the bug
Not sure if it's a bug or just my misinterpretation of the output, but the new
jq
has a "dirty" suffix, should that be the case?To Reproduce
Download the latest version of
jq
, then run:Produces:
Expected behavior
That should probably just print
jq-1.7
.Environment (please complete the following information):
Additional context
I have noticed it when testing an update of the Chocolatey package that I maintain.
The text was updated successfully, but these errors were encountered: