New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Disallow unnamed (autonamed) migrations? #5558
Comments
I like the idea of using django-test-migrations or a custom system check a lot better than overriding the management command or relying on commit hooks. But I definitely think this is something we should do. |
Good find, @Scotchester |
One minor request if we decide to implement this: can we make sure that devs can still use auto-named migrations when working locally? I often generate temporary migrations while working and only finalize when getting ready to commit/push up. We currently have some (admittedly hacky) logic that fails tox if there are missing migrations when run on Travis, but not when run locally -- perhaps we could do something similar with this check. |
We could prevent autogenerated migration filenames, if we want:
https://adamj.eu/tech/2020/02/24/how-to-disallow-auto-named-django-migrations/
The text was updated successfully, but these errors were encountered: