-
-
Notifications
You must be signed in to change notification settings - Fork 2
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
Add fail_level argument and deprecate fail_on_error #23
base: main
Are you sure you want to change the base?
Add fail_level argument and deprecate fail_on_error #23
Conversation
Co-authored-by: Marc Ransome <marc.ransome@fidgetbox.co.uk>
fail_level: | ||
Exit code for reviewdog when errors are found with severity greater than or equal to the given level [none,any,info,warning,error]. | ||
Default is `none`. |
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.
fail_level: | |
Exit code for reviewdog when errors are found with severity greater than or equal to the given level [none,any,info,warning,error]. | |
Default is `none`. | |
fail_level: | |
description: | | |
Exit code for reviewdog when errors are found with severity greater than or equal to the given level [none,any,info,warning,error]. |
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.
Fixes YML error.
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.
@gaurav-nelson The fail_level
input on line 26 needs to be indented two spaces in your suggested change.
Closes #24.
This PR has two commits to make it easier to review:
fail_level
option in the first commitfail_on_error=true
.If backwards-compatibility isn't important, we can just go with the first commit and reduce the code complexity.