This comes from a place of headaches: we're a large team, and our sprint are a month long, in that month we generate a lot of migrations, after a couple of sprints we see our tests take a real toll when running migrations, this is due to constantly adding columns/deleting columns, moving data around -- what normally happens with an ever changing app.
The way quashing migrations currently works is by an app by app, I'm proposing that if no arguments are supplied (no app_label, start_migration_name, migration_name) to squash the entire project, who's apps belong to the project of course. I'm hopping that I can get all the modifications already done to this project: https://github.com/kingbuzzman/django-squash and simply integrate it directly into the django source. I don't want to take such an undertaking and just have the PR be rejected. Is there any interest for this? Thanks, Javier Buzzi -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/ad3e7507-01af-49a6-ab15-e1b6d7d32bb7%40googlegroups.com.
