Add yaml linting check in CI #482
Merged
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.
This PR is auto-generated.
To avoid mistakes in the
yamlfiles, for example, duplicated keys or wrong indentation, we decided to add a lint check onyamlfiles.Additional to the
.yamllintfiles added in this pr, the following must be added as well:Example in `tests.yml create a new job:
.yamllint, you might want to ignore some folders. For examplenode_modulesin JS reposExample in
.yamllint:Since
yamllintis a python package, we cannot add a local check unless you download.yamllint.In which case, you can check if the yaml files are correctly linted by running the following command:
yamllint .Additionally, you can use the VSCode extension
YAMLby redhat which automatically highlights errors.To help users be aware of this, we recommend adding this to your contributing guide:
TODO
.yamllint