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
feat: migratePresets #10111
feat: migratePresets #10111
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just a docs issue, otherwise LGTM. Would prefer to wait for @HonkingGoose review
@@ -247,6 +247,24 @@ If left as default (null), a random short ID will be selected. | |||
|
|||
## logFileLevel | |||
|
|||
## migratePresets | |||
|
|||
Use this is you have repositories extending a particular preset but it has been removed or renamed. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is confusing. Typo?
Co-authored-by: HonkingGoose <34918129+HonkingGoose@users.noreply.github.com>
🎉 This PR is included in version 25.29.0 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
Changes:
Adds new config option
migratePresets
which allows for admin control of migrating removed or renamed presets.Context:
Closes #9209
Documentation (please check one with an [x])
How I've tested my work (please tick one)
I have verified these changes via: