-
Notifications
You must be signed in to change notification settings - Fork 80
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
[Feature Request] Fail on warnings #78
Comments
Hey! Neat idea – I'm definitely open to it, but I don't understand quite what it would do. Could you explain how the existing workflow would be different from this one? Maybe a PR makes the best sense to discuss the idea – let me know! |
I derp'd the followup on this, apologies! I'd close this, but it looks like @d-a-n almost(?) fixed this. |
This is one we are looking for in our project. Once we got to 0️⃣ |
Sure, if #109 doesn't do what you need, want to send a PR and we can review+merge? |
There's a nice switch for failing the build on a linter error. We would love to fail on any warnings in the PR only. Setting
warning_threshold: 0
in swiftlint itself limits is a bit too draconian for running CI test and development.In other words, how bout a
fail_on_warning: true
¯\_(ツ)_/¯Checking for interest. I can make a PR if it sounds like a good idea.
The text was updated successfully, but these errors were encountered: