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
Set --strict mode from configuration file #601
Comments
As another alternative: you can override a rule that defaults as a warning to be an error extends: default
rules:
comments:
level: error I do like the idea of adding top level configuration key like |
Hello, I allowed myself to rename the issue title, because most command-line flags ( Related to #348. I'm still not a fan of allowing |
I'm happy with the Issue title change to focus on the strict flag. What I would like to to is permanently set the exit code behaviour of yamllint. My context is for use with pre-commit, but it would also apply to other contexts where the exit code is tested. Setting
Setting Adrien, there's only one rigorous way to satisfy your curiosity: implement a config file setting for strict and then survey public repos to see how many people use it 😄 |
I've just found that there I would like yamllint to always run in pre-commit with the
--strict
option and looked to see if this option could be set in the.yamllint
configuration file. As far as I can tell, it can't, but the alternative of specifying the option as an argument in the pre-commit config file is good enough.A nice-to-have would be if the command line options could be set in the config file so behaviour is consistent between command line and pre-commit and the config is in one place.
I realise this would add complication, so I'd completely understand if this wasn't at all a priority. Thanks for writing yamllint and making it available, it's helped avoid trouble on more than one occasion!
The text was updated successfully, but these errors were encountered: