Prisma

just got a quick question about the migration engine: how are out-of-order migrations handled? e.g. I create and apply a migration to my dev environment, then before committing it, a colleague creates and pushes a different migration which is then ran through our CI/CD pipeline. Now the production database will be missing my migration if I try to push it! Will this cause `prisma migrate deploy` to fail?

Hey Roryl :wave: thanks for raising this! I’ve got a response from one of our engineers about your scenario:

&gt;  When you merge your branch with your migration after your colleague’s branch, both migrations will be on the main branch (presuming that’s the one that gets deployed). On the next deploy, your migration will be run, it doesn’t matter if the migration is before or after your colleague’s migrations in the migrations directory.


Thanks for the response. I went ahead and merged mine in and it worked like a charm.