ci(yamllint): add YAML linting (#838) #838
Open
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 to #836
Add YAML linting for all files except Helm chart files, which are linted by
helm lint
andct lint
(yamllint
does not understand templating language and fails with invalid syntax errors).Updatevalues-dev.yaml
file to pass linter checks.Add
.editorconfig
file with rules for various files. Adding also .go as I remember we were talking that it would be good if the file could be used everywhere, we'll be able to copypaste it to other repositories and there will be no need for changes if new files are introduced to the repository. Let me know if it is better to only add config only for the files that currently exist in the repository.For markdownlint, some rules were disabled because there will be to many changes to existing files (e. g. line length). Some rules do not work due to some specific contents in files, e. g. we have cron schedule defined (* * * * *) and markdownlint thinks this is emphasis (bold) and throws warning that there is a space between emphasis asterisks.