You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
m-ildefons
added a commit
to m-ildefons/hadolint-action
that referenced
this issue
May 8, 2021
- bump Hadolint version to 2.4.0
- change to debian based image
- add common config options
- expand integration tests for new options
fixes: hadolint#5fixes: hadolint#8fixes: hadolint#17fixes: hadolint#18fixes: hadolint#31
I use this action to keep trace of best practices. It should not stop the CI . Is is possible ?
Thanks!
The text was updated successfully, but these errors were encountered: