The Wayback Machine - https://web.archive.org/web/20211014044759/https://github.com/renovatebot/renovate/issues/11791
Skip to content
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

Add globalPresets and repoPresets to global config, deprecate direct extends use #11791

Open
rarkins opened this issue Sep 17, 2021 · 0 comments
Open

Comments

@rarkins
Copy link
Collaborator

@rarkins rarkins commented Sep 17, 2021

What would you like Renovate to be able to do?

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment