-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
Turn migratePresets
into a non-self-hosted property
#16605
Comments
doesn't make sense, as you still need to run renovate on it. so the request would be to allow migrating presets instead. so please update issue |
That's what |
So I think ideally it would have been called something like "remapPresets" because it doesn't migrate anything itself per se. But now that we have it, is it work renaming it? |
If the current name is confusing we should pick a better name, even if that means more work. Good names help to understand what the bot is going to do. 😄 Edit: I see we also mention Do you want a new issue to track renaming |
Yes, let's have a separate issue. We need to remember to migrate self-hosted config in this case |
Done, see:
Can you tell me where that todo belongs? I don't understand if it's for this issue or the new separate issue. 🙈 |
Within the same issue |
This would be really helpful, as it would allow rename files:
|
What would you like Renovate to be able to do?
The property
migratePresets
can be used to migrate presets (shocker, I know!). Today, the property is a self-hosted property. I'd like to suggest that I'd would be of more use if the property could also be set in a repo or preset context. More specifically: whenever implementable, it should be possible for a "legacy" preset to include amigratePresets
declaration about itself and its replacement, in order to auto-discover the new prefered situation.If you have any ideas on how this should be implemented, please tell us here.
Not really.
Is this a feature you are interested in implementing yourself?
Maybe
The text was updated successfully, but these errors were encountered: