Changes between Initial Version and Version 2 of Ticket #31402


Ignore:
Timestamp:
Mar 26, 2020, 2:13:59 AM (5 years ago)
Author:
Mariusz Felisiak
Comment:

Based on short discussion ​https://groups.google.com/d/msg/django-developers/wr8MYU-d8pU/f86jYOZ6AQAJ.

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #31402

    • Property Component Uncategorized → Core (Management commands)
    • Property Resolution → wontfix
    • Property Status new → closed
    • Property Summary Add --check flag to showmigrations → Add --check flag to migrate.
    • Property Type Uncategorized → New feature
    • Property Triage Stage Unreviewed → Accepted

  • Ticket #31402 – Description

    initial v2  
    1 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.
     1It 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.
    22
    3 `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
    4 
    5 One currently needs to parse output.  It seems like this would be universally useful
     3One currently needs to parse output.  It seems like this would be universally useful.
Back to Top