verify-ef-migration

To validate EF Core migrations for rollback safety, scan Migrations/*.cs files to confirm Down() methods are implemented and flag destructive operations like DropTable or DropColumn in Up() methods. This prevents data loss and deployment issues before merging database schema changes.

EF Core migrations should follow PascalCase and a verb-based naming scheme to prevent conflicts. Additionally, checking for duplicate timestamps across migration files avoids deployment conflicts and maintains a clean migration history.

Check for pending EF Core migrations by listing generated migrations not yet applied to the database. This ensures all new schema changes are accounted for and validated before a deployment cycle begins.

Yes, EF Core migration validation flags missing Down() methods to ensure migrations are safely reversible. Confirming Down() methods are implemented allows rolling back database schema changes safely if deployment issues occur.

Run EF Core migration checks before merging a pull request that includes new database schema changes. Automating these checks catches potential data loss risks, naming convention violations, and duplicate timestamps early in the development cycle.