A new `makemigrations`/`squashmigrations` option `--no-header` should
prevent the Django version and date from being written to migration file
header comments.
This will prevent unnecessary VCS churn in cases where that information
isn't required and will help to make migration files more deterministic.
--
Ticket URL: <https://code.djangoproject.com/ticket/30031>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
* owner: nobody => Dakota Hawkins
* status: new => assigned
--
Ticket URL: <https://code.djangoproject.com/ticket/30031#comment:1>
* type: Cleanup/optimization => New feature
* stage: Unreviewed => Accepted
--
Ticket URL: <https://code.djangoproject.com/ticket/30031#comment:2>
* has_patch: 0 => 1
Comment:
[https://github.com/django/django/pull/10743 PR]
--
Ticket URL: <https://code.djangoproject.com/ticket/30031#comment:3>
* stage: Accepted => Ready for checkin
--
Ticket URL: <https://code.djangoproject.com/ticket/30031#comment:4>
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"8d3147e130c4e5638fceb1e6125c040362ce12e8" 8d3147e1]:
{{{
#!CommitTicketReference repository=""
revision="8d3147e130c4e5638fceb1e6125c040362ce12e8"
Fixed #30031 -- Added --no-header option to
makemigrations/squashmigrations.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/30031#comment:5>