#28363: Allow naming the migration generated by squashmigrations
--------------------------------+------------------------------------
Reporter: Melvyn Sopacua | Owner: nobody
Type: New feature | Status: new
Component: Migrations | Version: master
Severity: Normal | Resolution:
Keywords: squashed | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
--------------------------------+------------------------------------
Changes (by Tim Graham):
* needs_better_patch: 0 => 1
* stage: Unreviewed => Accepted
Old description:
> PR: [https://github.com/django/django/pull/8087]
>
> Using --squashed-name the user can set the name of the resulting squashed
> migration. When she uses a scheme that matches public releases, this
> makes it easier to assess what has happened each release.
New description:
A new `--squashed-name` option allows setting the name of the resulting
squashed migration. When they use a scheme that matches public releases,
this makes it easier to assess what has happened each release.
[https://github.com/django/django/pull/8087 PR]
--
--
Ticket URL: <https://code.djangoproject.com/ticket/28363#comment:1>
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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/072.e76299f08fcf3f6f1970479f30821247%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
