Fixed #23302 -- Added --name/-n option to makemigrations command #3090
Conversation
| @@ -309,6 +309,11 @@ Note that this only works given two things: | |||
| that your database doesn't match your models, you'll just get errors when | |||
| migrations try to modify those tables. | |||
|
|
|||
| If you want to give migration a meaningful name instead of generated one, | |||
There was a problem hiding this comment.
the migration(s)
a generated
This is probably better suited to be documented in docs/ref/django-admin.txt where all the options of makemigrations are mentioned.
|
I think it's too late in the release cycle to add this to 1.7. So it'll need a The commit message should say "Fixed" not "Refs". See also our patch review checklist. |
rsalmaso
force-pushed
the
tickets/23302
branch
from
764546d
to
458bfbd
Compare
rsalmaso
changed the title
|
Updated PR |
|
Please do that and also rebase as it appears a conflicting change has been merged since this was submitted. |
rsalmaso
force-pushed
the
tickets/23302
branch
from
458bfbd
to
a1650c6
Compare
|
PR updated |
rsalmaso
force-pushed
the
tickets/23302
branch
3 times, most recently
from
edef8c9
to
db5f68d
Compare
|
|
||
| .. django-admin-option:: --name, -n | ||
|
|
||
| The ``--name`` option give migration(s) a custom name instead of a generated one. |
|
Please add 1.8 release notes and uncheck "Patch needs improvement" on the ticket when it's updated, thanks. |
rsalmaso
force-pushed
the
tickets/23302
branch
from
db5f68d
to
874f0ac
Compare
|
PR and ticket updated |
|
buildbot, add to whitelist. |
|
merged in 1435cfb, thanks. |
Add a --name option to makemigrations command
Refs https://code.djangoproject.com/ticket/23302