Deprecate use of extends in global config and replace with globalPresets and repoPresets. Current extends behavior will map to repoPresets while new optional globalPresets will mean the preset is resolved during global config resolution, not repo config resolution.
If you have any ideas on how this should be implemented, please tell us here.
Note in extends that it is for repo config only and to use the others for global
If found in global, migrate it to repoPresets and WARN
ignorePresets in global config apply only to globalPresets
Document the differences well, e.g. repoPresets are passed through to repo config so can only be overridden by repo config including ignorePresets. globalPresets are resolved during global config resolution and so cannot be ignored by repo config directly
Is this a feature you are interested in implementing yourself?
No
The text was updated successfully, but these errors were encountered:
What would you like Renovate to be able to do?
Deprecate use of
extendsin global config and replace withglobalPresetsandrepoPresets. Currentextendsbehavior will map torepoPresetswhile new optionalglobalPresetswill mean the preset is resolved during global config resolution, not repo config resolution.If you have any ideas on how this should be implemented, please tell us here.
extendsthat it is for repo config only and to use the others for globalrepoPresetsand WARNglobalPresetsrepoPresetsare passed through to repo config so can only be overridden by repo config includingignorePresets.globalPresetsare resolved during global config resolution and so cannot be ignored by repo config directlyIs this a feature you are interested in implementing yourself?
No
The text was updated successfully, but these errors were encountered: