-
-
Notifications
You must be signed in to change notification settings - Fork 241
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
EXTENDS
in .mega-linter.yml
: Properties from extended file override properties in extending file
#1516
Comments
This should indeed be the contrary: local config that overriddes default config from extended file ^^ |
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 |
Should probably stay open. |
Agreed :) |
No worries, looking forward to v6. |
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 |
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 |
Ensure that local config keys overwrite inherited config keys rather than the other way around.
Ensure that local config keys overwrite inherited config keys rather than the other way around.
Ensure that local config keys overwrite inherited config keys rather than the other way around.
* Correct casing from "VsCode" to "VSCode" * Document EXTENDS inheritance order * Correct behavior of EXTENDS (#1516) Ensure that local config keys overwrite inherited config keys rather than the other way around. * fix jscpd config quick build Co-authored-by: nvuillam <[email protected]>
Describe the bug
To simplify the configuration of MegaLinter across multiple repos I want to have one base config in my
.github
repo and then have a short configuration in each other repo that adds properties or overrides the ones from the base config. For example, in one repository I want to override theFILTER_REGEX_EXCLUDE
property:However, this does not seem to work as expected: The
FILTER_REGEX_EXCLUDE
property from the extended config overrides the property defined here rather than the other way around. This means the base config can only contain properties that I know I'll never want to override.To Reproduce
Steps to reproduce the behavior:
Expected behavior
The property in the extending file should have precedence.
Additional context
At first glance this seems to cause this behavior: https://github.com/megalinter/megalinter/blob/100a4d937a48c79e0eb5de8325d4d2b22601d861/megalinter/config.py#L82
The text was updated successfully, but these errors were encountered: