#32217: Add warning about missing 'migrations' package to migration docs
-------------------------------------+-------------------------------------
Reporter: Tim McCurrach | Owner: Tim
Type: | McCurrach
Cleanup/optimization | Status: closed
Component: Documentation | Version: 3.1
Severity: Normal | Resolution: invalid
Keywords: | Triage Stage:
| Unreviewed
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Mariusz Felisiak):
* status: assigned => closed
* resolution: => invalid
Comment:
This behavior is already documented in the `makemigrations`
[https://docs.djangoproject.com/en/3.1/ref/django-admin/#makemigrations
docs]:
{{{
To add migrations to an app that doesn't have a migrations directory, run
makemigrations with the app's app_label.
}}}
and in the `MIGRATION_MODULES`
[https://docs.djangoproject.com/en/3.1/ref/settings/#std:setting-
MIGRATION_MODULES docs]:
{{{
If you provide the app_label argument, makemigrations will automatically
create the package if it doesn’t already exist.
When you supply None as a value for an app, Django will consider the app
as an app without migrations regardless of an existing migrations
submodule.
}}}
I think that's enough.
--
Ticket URL: <https://code.djangoproject.com/ticket/32217#comment:2>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/071.a539de0ab93c0561f49f24526fa69dd3%40djangoproject.com.
