HDDS-10351. Add GitHub Actions check for yaml formatting. #87
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.
What changes were proposed in this pull request?
Use yamllint to to check yaml configuration files. This isn't a very important check IMO since most website changes will not be editing yaml files, and the
_category_.yml
files are pretty simple. However yamllint is already in the GitHub actions Ubuntu runner so it's low effort to add this check.I set the yaml linting rules based on what I usually follow but I don't have strong opinions on them as long as they are consistent.
What is the link to the Apache Jira?
HDDS-10351
How was this patch tested?
Failing CI run with yamllint added but existing errors not fixed: https://github.com/errose28/ozone-site/actions/runs/8427283082/job/23077474962
CI on this PR should pass with the fixed yaml files.