Feedback on schema migration strategy

Summary _( Already posted this in community.directus.io but without luck. )_ I'm currently evaluating if Directus could be a solution for upcoming projects and would love some feedback on my understanding of schema migrations. ---------- I’m currently trying to wrap my head around the best practice approach for schema sync and migration between development and production environments (both in docker), CI/CD and multiple development machines. From the docs and github discussions I would try the following, does this makes sense? Would this work as intended? All schema (collections, roles, flows) development happens locally on my machine. Whenever there are changes to the schema, I run a migration via the Schema API endpoints: 1. Schema sync development ↔ production /schema/snapshot on the local instance and /schema/diff and /schema/apply on the production instance. 2. Schema sync development ↔ git repo To check in the schema into my repo we can use snapshots…