Open
Description
Describe the bug
When you extend a config in a different repository that extends a config within said repository, the keys from the parent config are properly incorporated, but the grandparent config is completely ignored.
To Reproduce
Steps to reproduce the behavior:
- Extend a config such as ours, which extends a local config.
- Run MegaLinter on your project.
- Observe that none of the settings in the base config are respected.
Expected behavior
I expected the inheritance to apply recursively.
Additional context
There were recent fixes for extending local files and extending recursively, but the case where both features are combined isn't handled properly. Renovate has sophisticated support for config inheritance, which may be a helpful reference. One solution might be to specify the base (e.g., repo) URL in one config key and the path relative to the base URL in another.