-
Notifications
You must be signed in to change notification settings - Fork 60
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
tests/git-helper.sh: fix yq checking #342
tests/git-helper.sh: fix yq checking #342
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
good catch
lgtm |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good catch
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Apart from possible typo fix (yq
->jq
) in the commit header, LGTM. Thanks
Oh true, I missed that. @wainersm could you please update the commit message? |
`[ ! command -v jq &> /dev/null ]` doesn't work for checking the existing of jq because if enclosed in `[]` it won't check the return code of `command`. Signed-off-by: Wainer dos Santos Moschetta <[email protected]>
6135fa3
to
2306239
Compare
ops... fixed the commit message! Thanks @stevenhorsman ! |
[ ! command -v jq &> /dev/null ]
doesn't work for checking the existing of yq because if enclosed in[]
it won't check the return code ofcommand
.Found this problem when running the CI jobs for PR #338.
I don't know why on previous execution jq existed on the system so that we didn't catch the issue before.