Of course, you should have one in your local tools and CI pipeline to ensure that your [[YAML]] is always correct.
You can't just use "one" solution though== Manually fix errors==Unfortunately, <tt>yamllint</tt> does not fix your file for you. The leading GPL linter is based on PythonThere could be ambiguities about the proper fix, so depending on your code repo, you may instead want need to use a JavaScript or PHP implementation. Thus, tools like [[wp:Grunt do the fix(softwarees)]] may be used to automate JSHint linting in [[JavaScript]] projects<ref>https://www.codereadability.com/jshint-with-grunt/</ref>yourself.
== Many linters ==
You can't just use "one" solution either<ref>https://phabricator.wikimedia.org/T95890</ref>. The leading GPL linter is based on Python, so depending on your code repo, you may instead want to use a JavaScript or PHP implementation. Thus, tools like [[wp:Grunt (software)]] may be used to automate JSHint linting in [[JavaScript]] projects<ref>https://www.codereadability.com/jshint-with-grunt/</ref>.
== Source, Docs and Reading ==
* https://github.com/adrienverge/yamllint
* https://yamllint.readthedocs.io/en/stable/
* https://www.redhat.com/sysadmin/check-yaml-yamllint
{{References}}
