-
-
Notifications
You must be signed in to change notification settings - Fork 653
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
Look for .sqlfluffignore in current directory #2573
Look for .sqlfluffignore in current directory #2573
Conversation
[os.path.basename(ignore_file_path)], | ||
) | ||
for ignore_file_path in ignore_file_paths | ||
] |
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.
This change is not as big or complex as it first appears. I basically just moved lines 853 - 867 below, out of the if
statement.
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.
LGTM assuming tests pass)
(a lot less changes when you hide whitespace changes btw)
A Windows test is failing. Will investigate. Probably something to do with the Windows-specific concept of "current drive", and having a current directory per drive, which is different from Unix. Hopefully nothing too tricky. Debugging test failures on GitHub is 🤢 . |
I had problems with this on the original move to GitHub Actions. I add the following note to
Wonder if it's something similar here? |
I think it's similar.
I found a possible fix: calling |
…ctory' of https://github.com/barrywhart/sqlfluff into bhart-issue_556_look_for_sqlfluffignore_in_current_directory
Codecov Report
@@ Coverage Diff @@
## main #2573 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 163 163
Lines 11851 11852 +1
=========================================
+ Hits 11851 11852 +1
Continue to review full report at Codecov.
|
Brief summary of the change made
Fixes #556
Are there any other side effects of this change that we should be aware of?
Pull Request checklist
Please confirm you have completed any of the necessary steps below.
Included test cases to demonstrate any code changes, which may be one or more of the following:
.yml
rule test cases intest/fixtures/rules/std_rule_cases
..sql
/.yml
parser test cases intest/fixtures/dialects
(note YML files can be auto generated withtox -e generate-fixture-yml
).test/fixtures/linter/autofix
.Added appropriate documentation for the change.
Created GitHub issues for any relevant followup/future enhancements if appropriate.