title: Previous incompatible ef core migrations, how to correctly bypass them in a CI/CD system?
body: <p>So I have a <code>Dev</code> and a <code>Staging</code> environments (Azure DevOps).</p>
  
  <p>The <code>CD</code> pipeline generates a migrations script of the <code>Dev</code> environment <code>DB</code>. 
  This latter is executed by <code>Staging release</code> pipeline, to put the <code>Staging</code> <code>DB</code> up to date.</p>
  
  <p>The generated script contains all the migrations (it is not a <code>--from</code>, <code>--to</code> script).</p>
  
  <p>Although the command generating the migrations script uses the <code>--idempotent</code> parameter, to avoid executing migrations that were already brought to the <code>Staging</code> <code>DB</code>, some queries would still cause errors (when being syntax checked), for instance when they use some table properties that don't exist any more.</p>
  
  <p>Is there any way to completely bypass/NotExecute the already applied migrations ?</p>
  
  <p>I don't want to go with the <code>--from</code>, <code>--to</code> when generating the migration script, as the CD pipeline(using the <code>Dev</code> environment) can't know about what's been applied or not in the <code>Staging</code> environment. That would necessit writing a complex dedicated Powershell script (not time for it).</p>