A linter for YAML files.
Go to file
Adrien Vergé 918f15b68d Make syntax errors prevail over yamllint 'warnings'
When both a syntax error (unability to parse a document) and a cosmetic
yamllint problem are found at the same place, the yamllint problem had
the priority -- and the syntax error was not displayed.

This had the following problem: if a rule is at the 'warning' level, its
problems will not make the `yamllint` script return a failure return
code (`!= 0`), even when it should (because there was a syntax error,
precisely).

This commit changes this behavior by preferring yamllint problems only
when they have the 'error' level.
2016-01-15 18:46:49 +01:00
bin Initial commit 2016-01-14 10:46:14 +01:00
tests Don't treat non-importable YAML as syntax error 2016-01-15 18:46:49 +01:00
yamllint Make syntax errors prevail over yamllint 'warnings' 2016-01-15 18:46:49 +01:00
.gitignore Initial commit 2016-01-14 10:46:14 +01:00
.travis.yml Tests: Travis and Coveralls integration 2016-01-14 10:46:16 +01:00
LICENSE Initial commit 2016-01-14 10:46:14 +01:00
README.md Distribution: Update program description 2016-01-14 21:08:10 +01:00
setup.py Tests: Travis and Coveralls integration 2016-01-14 10:46:16 +01:00

yamllint

A linter for YAML files.

Build Status Coverage Status