#31402: Add --check flag to migrate.
-------------------------------------+-------------------------------------
Reporter: nickname123 | Owner: nobody
Type: New feature | Status: closed
Component: Core (Management | Version: 3.0
commands) |
Severity: Normal | Resolution: wontfix
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by felixxm):
* stage: Unreviewed => Accepted
Old description:
> It would be helpful if there was a flag for `showmigrations` that acted
> similar to `makemigrations --check` that could be used to stop CI from
> deploying an application automatically when database migrations would be
> needed.
>
> `showmigrations` is preferred to `migrate` for this purpose so a typo
> doesn't accidentally run the migrations but I suppose that isn't super
> important
>
> One currently needs to parse output. It seems like this would be
> universally useful
New description:
It would be helpful if there was a flag for `migrate` that acted similar
to `makemigrations --check` that could be used to stop CI from deploying
an application automatically when unapplied migrations exist.
One currently needs to parse output. It seems like this would be
universally useful.
--
Comment:
Based on short discussion https://groups.google.com/d/msg/django-
developers/wr8MYU-d8pU/f86jYOZ6AQAJ.
--
Ticket URL: <https://code.djangoproject.com/ticket/31402#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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/069.4f36c7a44a9dc4c2cb0db3194ea1a030%40djangoproject.com.
