-
-
Notifications
You must be signed in to change notification settings - Fork 47
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
[BUG]: Booleans written as strings are not handled correctly #447
Comments
Thanks for the report @frouioui! FWIW this is a GHA-ism, not a YAML-ism: Regardless, this is indeed a bug in |
That's a good point, thanks for the clarification 🙇🏻 |
Fixes #447. Signed-off-by: William Woodruff <[email protected]>
#448 should fix this! |
Awesome, thanks for the quick turnaround! |
Pre-submission checks
Expected behavior
When I write a boolean value between quotes (e.g.
'false'
) I expect it to be treated as a boolean equal to false, and not a string containingfalse
. Which is what yaml and GHA do.I want to be able to write the following snippet in my workflow and have
zizmor
not issue any warning saying thatpersist-credentials
should be set tofalse
.Actual behavior
Right now
zizmor
emits a warning when using the snippet pasted above:Despite the warning, the value is correctly set to
false
on GitHub Actions:Reproduction steps
Use the following step:
Run
zizmor
on the yaml file and observe the warning.Logs
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: