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
disable migrations config #14593
disable migrations config #14593
Conversation
@alexandrebodin any news on this PR please ? |
I wasn't added as reviewer so didn't see this PR. |
Codecov ReportBase: 60.49% // Head: 60.49% // No change to project coverage 👍
Additional details and impacted files@@ Coverage Diff @@
## main #14593 +/- ##
=======================================
Coverage 60.49% 60.49%
=======================================
Files 1352 1352
Lines 33179 33179
Branches 6339 6340 +1
=======================================
Hits 20070 20070
+ Misses 11274 11273 -1
- Partials 1835 1836 +1
Flags with carried forward coverage won't be shown. Click here to find out more.
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
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.
Ok so general thought about the config name. we like to make the naming more declarative instead of enableX disableX, what do you think of runMigrations: true|false
?
Hey I'm seeing the CLA-sign not very happy probably because you used 2 different users to commit can you check that please :) |
Hi! I'm Pierre, a technical writer at Strapi. Thank you for the contribution, @gary-alway! Would you like to do it yourself, or would you rather have me handle it? 🙂 |
thanks @pwizla, I will have a go at updating the docs |
Hi! The related documentation PR is approved. Just waiting for this PR to be merged in strapi/strapi before merging the docs one :) |
thanks @pwizla, @alexandrebodin 🚀 |
What does it do?
runMigrations
settings keyWhy is it needed?
Model migrations mean that old migrations might not be compatible with the current schema which makes local development fail for fresh dbs.
How to test it?
Passing
runMigrations
=false
will prevent any migration scripts from running, by default migrations remain enabled.Related issue(s)/PR(s)
strapi/documentation#1353