-
-
Notifications
You must be signed in to change notification settings - Fork 189
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
fix: exit with 1 for failing validations #1068
fix: exit with 1 for failing validations #1068
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.
Welcome to AsyncAPI. Thanks a lot for creating your first pull request. Please check out our contributors guide useful for opening a pull request.
Keep in mind there are also other channels you can use to interact with AsyncAPI community. For more details check out this issue.
While the implementation should be straight-forward, the tests somehow fail and report |
Test are all green locally now, so this would be ready to review. |
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.
I just wanted to open the issue for it and I salute you for fixing it <3
Quality Gate passedKudos, no new issues were introduced! 0 New issues |
@Souvikns @magicmatatjahu @derberg is there anything I should do to proceed with the PR? |
/rtm |
🎉 This PR is included in version 1.4.3 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Description
Exit the
validate
with 1 for failing validations. Failing validations should exit with code 1 so they can be used in CI and also comply with the commands' documentation.Related issue(s)
Resolves #861