ef-migration-plan

To plan a zero-downtime EF Core migration, gather change details and assess risks to determine if multi-step deployment sequences are needed. The workflow enforces hard stops and requires a MIGRATION_PLAN.md to safely orchestrate provider-specific changes.

Before deploying an EF Core migration, review the generated migration for potential data loss, performance impact, and provider compatibility. This review phase validates changes against provider-specific behavior to detect zero-downtime risks.

To generate a safe deployment script for EF Core migrations, use the deploy phase to produce scripts with rollback guidance and pre-flight checks. It outputs a concrete checklist to ensure safe execution across projects using EF Core.

You need a MIGRATION_PLAN.md for EF Core database changes when the planning phase detects zero-downtime risks. The workflow enforces this document as a hard stop to ensure multi-step deployment sequences are properly orchestrated.

Yes, this migration workflow validates changes against provider-specific behavior. During the review phase, it inspects generated migrations to ensure compatibility with the specific database provider used by your EF Core project.