#34051: makemigrations --check generating migrations is inconsistent with other
uses of --check
-------------------------------------+-------------------------------------
Reporter: Jacob Walls | Owner: Jacob
Type: | Walls
Cleanup/optimization | Status: closed
Component: Migrations | Version: dev
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Daniel Hahler):
I was using `--check --dry-run` to see missing migrations on CI already,
which now becomes silent.
Would it make sense to have migrations still being written/printed in case
`--dry-run` is used.
Or is there another option to get the desired behavior on CI?
(You could use `--check` first an in case of exiting with 1 use `--dry-
run` alone, but I think the old behavior was good).
I am using also `-v3` to make it very verbose - maybe that could be taken
into consideration also.
--
Ticket URL: <https://code.djangoproject.com/ticket/34051#comment:7>
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/0107018d1cc9c53d-01f250fd-6e0f-447f-bae3-dddf89a0f4e1-000000%40eu-central-1.amazonses.com.
