ansible/community.general
1
0
Fork 0
mirror of https://github.com/ansible-collections/community.general.git synced 2024-09-14 20:13:21 +02:00
Code Releases Activity
community.general/.yamllint

20 lines
534 B
Text
Raw Normal View History

Fix YAML source and check it on Shippable (#15678) Fix YAML source and check it on Shippable
2016-06-04 19:58:17 +02:00
extends: default
rules:
Lint YAML files under test/ This commit extends YAML linting by enabling standard rules from the `yamllint` tool [1]. Since syntax errors and key duplicates are already checked since 4d48711, this change only adds detection for cosmetic problems. It also narrows checks to the test/ dir only. The main goal is to prevent future problems to enter the code base without being noticed. While it would be a huge effort to be PEP8 compliant, it is relatively easy to have correct YAML style *now* and prevent future errors by enabling linting. Note: for those (like me) caring about code attribution: use `git blame -w` to ignore whitespace-only changes. Note: I disabled some linting checks (such as indentation), they can be enforced in the future if needed. Similarly, current checks can also be disabled. See the `.yamllint` file. [1]: https://yamllint.readthedocs.io/
2016-04-18 17:25:39 +02:00
braces: {max-spaces-inside: 1, level: error}
brackets: {max-spaces-inside: 1, level: error}
colons: {max-spaces-after: -1, level: error}
commas: {max-spaces-after: -1, level: error}
Fix YAML source and check it on Shippable (#15678) Fix YAML source and check it on Shippable
2016-06-04 19:58:17 +02:00
comments: disable
comments-indentation: disable
document-start: disable
Lint YAML files under test/ This commit extends YAML linting by enabling standard rules from the `yamllint` tool [1]. Since syntax errors and key duplicates are already checked since 4d48711, this change only adds detection for cosmetic problems. It also narrows checks to the test/ dir only. The main goal is to prevent future problems to enter the code base without being noticed. While it would be a huge effort to be PEP8 compliant, it is relatively easy to have correct YAML style *now* and prevent future errors by enabling linting. Note: for those (like me) caring about code attribution: use `git blame -w` to ignore whitespace-only changes. Note: I disabled some linting checks (such as indentation), they can be enforced in the future if needed. Similarly, current checks can also be disabled. See the `.yamllint` file. [1]: https://yamllint.readthedocs.io/
2016-04-18 17:25:39 +02:00
empty-lines: {max: 3, level: error}
hyphens: {level: error}
Fix YAML source and check it on Shippable (#15678) Fix YAML source and check it on Shippable
2016-06-04 19:58:17 +02:00
indentation: disable
key-duplicates: enable
line-length: disable
new-line-at-end-of-file: disable
new-lines: {type: unix}
trailing-spaces: disable
Lint YAML files under test/ This commit extends YAML linting by enabling standard rules from the `yamllint` tool [1]. Since syntax errors and key duplicates are already checked since 4d48711, this change only adds detection for cosmetic problems. It also narrows checks to the test/ dir only. The main goal is to prevent future problems to enter the code base without being noticed. While it would be a huge effort to be PEP8 compliant, it is relatively easy to have correct YAML style *now* and prevent future errors by enabling linting. Note: for those (like me) caring about code attribution: use `git blame -w` to ignore whitespace-only changes. Note: I disabled some linting checks (such as indentation), they can be enforced in the future if needed. Similarly, current checks can also be disabled. See the `.yamllint` file. [1]: https://yamllint.readthedocs.io/
2016-04-18 17:25:39 +02:00
truthy: disable
Copy permalink