Hi everyone, is there a way to ignore/bypass prisma's

The migration ... was modified after it was applied. We need to reset the database

error in dev? I'm running

prisma migrate dev --create-only

. I've already done a manual check to verify that the db and migrations are in-sync. I want to avoid re-seeding my dev database - there's a lot of test data and re-seeding it in a reasonable amount of time would involve a lot of index hackery.