-
-
Notifications
You must be signed in to change notification settings - Fork 244
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
MegaLinter ignores linter config in workspace when LINTER_RULES_PATH
is set
#4254
Comments
This issue has been automatically marked as stale because it has not had recent activity. If you think this issue should stay open, please remove the |
Is the probem still happening ? :) |
@nvuillam Yes. Here is a demo workflow run:
Note the message Is the |
@liblaf Sorry, the order is the following, and we won't change it to not mess with all MegaLinter configurations following this order :)
|
Describe the bug
I am expecting MegaLinter to search for linter config files in the following precedence:
GITHUB_WORKSPACE
LINTER_RULES_PATH
However, MegaLinter seems to ignore config files in workspace when
LINTER_RULES_PATH
is set.To Reproduce
Here is the demo workflow run.
Expected behavior
There should be no errors since
F401
is ignored in.ruff.toml
. However,.ruff.toml
under repository root seems not to be used by MegaLinter.Additional context
Setting
PYTHON_RUFF_CONFIG_FILE: LINTER_DEFAULT
in.mega-linter.yaml
can solve the issue.The text was updated successfully, but these errors were encountered: