It would be handy to have these new migrations created inside my project's
folder so they can be committed to version control and not be lost if I
blow my virtualenv away.
I'm not sure how this would work as I've tried manually moving them to my
project but am unsure how to set the dependency back to the initial app
migration, but this at least should be highlighted as a potential issue.
--
Ticket URL: <https://code.djangoproject.com/ticket/24540>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
* needs_better_patch: => 0
* needs_tests: => 0
* needs_docs: => 0
--
Ticket URL: <https://code.djangoproject.com/ticket/24540#comment:1>
* status: new => closed
* resolution: => invalid
Comment:
You can use the `MIGRATION_MODULES` setting to create migrations inside
your project.
--
Ticket URL: <https://code.djangoproject.com/ticket/24540#comment:2>