#36185: manage.py migrate --check --prune actually prunes, which is surprising
-----------------------------+--------------------------------------
     Reporter:  Ari Pollak   |                    Owner:  (none)
         Type:  New feature  |                   Status:  closed
    Component:  Migrations   |                  Version:  5.1
     Severity:  Normal       |               Resolution:  wontfix
     Keywords:               |             Triage Stage:  Unreviewed
    Has patch:  0            |      Needs documentation:  0
  Needs tests:  0            |  Patch needs improvement:  0
Easy pickings:  0            |                    UI/UX:  0
-----------------------------+--------------------------------------
Comment (by Natalia Bidart):

 Replying to [comment:2 Adam Johnson]:
 > Since it doesn’t make sense to use the options together

 Could you elaborate why? I do think it makes sense in some cases, such as
 CI and cleanup jobs...
-- 
Ticket URL: <https://code.djangoproject.com/ticket/36185#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 visit 
https://groups.google.com/d/msgid/django-updates/010701955cdfd071-68f71a05-cdb1-4848-a837-30c5211a888a-000000%40eu-central-1.amazonses.com.

Reply via email to