In Symfony, is it better to create one large migration or many small ones (separate for each table)?

Question

symfony

How is it better to create a migration using Symfony? And why?

Answer 1

Migration means one change, one feature. It must be reversible and contain all data.
Therefore, the feature should be small, and the migration should include all tables that have changed

Answer 2

Symfony has nothing to do with it.
If within a specific task you need several tables, create them in one migration. Dividing into files for the sake of sharing is a very so-so idea.
If you need several different migration steps as part of the deployment, you should separate them.