Closed pascalandy closed 3 years ago
Ideally this would be configurable. In my use cases I have separate github actions and want the ones that fail to have non-zero exit.
That said, there are use cases where you want the tool to run on an existing file but you don't want it to be considered a failure because you are in an ongoing effort to move to best practices.
If you have a few known issues, then you could just have them ignored in a config file and then when you want to validate, do a custom run without the config file to double check divergence from best practices.
I use this action to keep trace of best practices. It should not stop the CI . Is is possible ?
Thanks!