I need help formulating a strategy for handling situations where two or more team members create an EF migration independently and for different reasons. Every single time we’ve had this scenario so far, it completely messed up the DB snapshot as well as on occasion the migration too. Our migrations are more complex than the normal boilerplate since it contains seed data and some other things I can’t discuss. But in essence what happens is that when we have two or more migrations, there are always merge conflictsin our snapshots and no clear path to resolve them.

I think it’s mostly due to having one snapshot but having