-
-
Notifications
You must be signed in to change notification settings - Fork 227
Mislabeled warning #494
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
Comments
I'm a bit confused, failing on only errors should be the default behavior. |
I believe it's not failing on errors, we got:
and it did not end as error |
any ideas? @dbanty |
I haven't forgotten about you, I've just been on vacation 🏖. I should be able to reproduce and fix it this weekend. |
Thank you! |
Well I found the issue 😓. Turns out that thing labeled "ERROR" is actually a warning... it can't generate the one endpoint but it can keep generating others so it actually just skips that. Clearly it used to be an error at some point and I never updated the text... confusing. I'm going to update the text for 0.10.5. I should probably have a clearer indication of the level of any given message in a future change. |
Thanks dbanty! Could you also review openapi-generators/openapi-python-client-action#4, it's related to the same problem I found. |
Is your feature request related to a problem? Please describe.
There is
--fail-on-warning
that fails for warnings or errors, but no--fail-on-error
only to fail for errors (ignoring warnings)Describe the solution you'd like
--fail-on-error
only to fail for errors (ignoring warnings)Describe alternatives you've considered
None
Additional context
To make a GitHub Action fail for errors only.
The text was updated successfully, but these errors were encountered: