Search for config with the yml/yaml extension #4416
Merged
Conversation
This file contains hidden or 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
cornfeedhobo
force-pushed
the
support-cfg-yaml-ext
branch
from
97d2702 to
d3f0946
Compare
shatakshiiii
force-pushed
the
support-cfg-yaml-ext
branch
from
d3f0946 to
2922230
Compare
audgirka
approved these changes
Dec 4, 2024
ssbarnea
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Suggestion cannot be applied right now. Please check back later.
Put simply, it's extremely annoying to configure every editor to associate
.ansible-lintwithyaml. It'd be a lot easier if this tool accepted a sane file extension. This PR makes that happen!.ansible-lint.yml.ansible-lint.yamlDEFAULT_KINDSwhich wasn't flagging.config/ansible-lint.yamlas aansible-lint-config