#31402: Add --check flag to migrate.
-------------------------------------+-------------------------------------
Reporter: nickname123 | Owner: nobody
Type: New feature | Status: new
Component: Core (Management | Version: 3.0
commands) |
Severity: Normal | Resolution:
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 thenewguy):
* status: closed => new
* resolution: wontfix =>
Old 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.
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.
This is different from `makemigrations --check` because the new command
flag would tell us if we need to *run* any migrations where as
`makemigrations --check` tells us if we need to *create* any migrations.
One currently needs to parse output. It seems like this would be
universally useful.
--
--
Ticket URL: <https://code.djangoproject.com/ticket/31402#comment:3>
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/069.6e4b569a93678bc18368f41c016298ec%40djangoproject.com.
