-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
init changelog config should be in proper yaml #91
Comments
How do you define "proper YAML"? All YAML parsers I know off don't require the above things your linter mentioned. |
Let me check it on whats enabled in ansible-lint Prod profile, as this is an Ansible Tool, that is what it should adhere to. |
its in our yaml lint rules |
Closing since this seems more like a problem with ansible-lint or yamllint. |
We use PyYAML to dump yaml files. The indentation linting errors are from that. ruamel.yaml does handle this properly, but I don't think this on its own is a compelling reason to switch yaml libraries and pull in another dependency. Fix these linting errors by hand if you'd like or just add that file to the linter's ignore list. The file is still perfectly valid yaml. It would be trivial to add |
I don't see why it is necessary, but that would be possible. |
Let me get back to this, as I think some of it was our own rules, and some of it was ansible lint. if its done with the pyaml dump thats fine, just thought we should be putting out things that eat our own dogfood with ansilbe-lint. |
the requirement of the --- and ... is in our rules because it is correct yaml syntax but is not part of the production profile so I think it is most likely fine to just leave it how it is because most people don't seem to care about requiring --- and ... |
Added changelog to a new collection then ran ansible-lint against it. Had the following errors:
This should be updated to be proper yaml.
The text was updated successfully, but these errors were encountered: