-
Notifications
You must be signed in to change notification settings - Fork 637
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
Fix get_yaml_files to return all configured files #1549
Fix get_yaml_files to return all configured files #1549
Conversation
The issue was introduced with ansible#1473 and only affects setups without a git repo and when custom kinds are used.
@sengaya Is not clear from the description but my impression is that this fixed the issue where If so, maybe we should also rename |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fix the linting and explain the reasoning a little bit better. Other than this is looks like a good bugfix.
@ssbarnea thanks for the feedback. I would not rename it to But after looking again at |
Apply the patterns defined in DEFAULT_KINDS as well as custom defined yaml patterns and only return these files.
@ssbarnea After digging a bit deeper into the code base I could come up with a solution how to apply the default and custom yaml patterns. Let me know what you think. |
Address bug related to detection of lintable files when run outside a git repository. - extend list of exclusions with few common directiories - allow linter to identify any file type, not only those with yaml/yml extension (matches behavior of git ls-files variant) - improve logging messages Closes: #1549
Obsoleted by #1557 |
Address bug related to detection of lintable files when run outside a git repository. - extend list of exclusions with few common directiories - allow linter to identify any file type, not only those with yaml/yml extension (matches behavior of git ls-files variant) - improve logging messages Closes: #1549
The issue was introduced with #1473 and only affects setups without a
git repo and when custom kinds are used.