Disable YAML linting in ansible-lint #3370
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Ansible Lint's YAML linting is not needed since super-linter already contains yamllint.
akikanellis
requested review from
admiralAwkbar,
lindluni,
zkoppert,
nemchik,
Hanse00,
GaboFDC and
ferrarimarco
as code owners
|
@akikanellis Very good catch and I think this would be a better behavior |
admiralAwkbar
approved these changes
Sep 28, 2022
ferrarimarco
approved these changes
Sep 29, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Ansible Lint's YAML linting is not needed since super-linter already contains yamllint. This also fixes the conflict explained in #2818 between Ansible Lint's yamllint and super-linter's yamllint.
Fixes #2818
Proposed Changes
Readiness Checklist
Author/Contributor
Reviewing Maintainer
breakingif this is a large fundamental changeautomation,bug,documentation,enhancement,infrastructure, orperformance