add Github Super-Linter action #482
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Related: 8c1cd7d Ensure that lint errors like trailing whitespace are not added going forward to prevent errors with consistent parse/dump of YAML files.
|
I ended up adding |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Related: 8c1cd7d, #481
Ensure that lint errors like trailing whitespace are not added going
forward to prevent errors with consistent parse/dump of YAML files.
In its current state it will run all of the linters listed here only on files added/changed in a PR
If we just want it to run yamllint (or rubocop, etc.) then we can specify which linters to run