Suppose you create your migration files using:

prisma migrate dev --create-only --preview-feature

Then when you run prisma migrate dev --preview-feature to apply the changes (without changing the SQL), you are prompted for a migration name. Once entered, everything applies but you end up with a migration file that just drops and adds FK's.

I assume this is because you're expecting --create-only to only be used as a precursor to manual sql changes being made to the generated SQL files but that's not the case with me - it's just easier to build into my flow and I also like to check the SQL before it's applied.

If the SQL hasn't changed, I wouldn't expect to be prompted to enter a new migration name.