Hi - new user here. When deploying to prod I plan to have my deploy script call dotenv -e .env -e .env.production -- npx prisma migrate deploy But then I read I need to call resolve too? So does resolve update files that I have to check back in? Or does resolve update the migrations table? Because my production server does not have github upload rights for the migrations folder, I do a git clone on each prod push. Is it customary to call the resolve from the production server after deploy or do most people call resolve from the development branch? Do I have to wait for the deploy to happen or can I just do resolve locally after pushing migrations to prod? If there is a blog article or help file explaining the deploy process that would be very helpful.

Hey 👋 It seems you are referring to https://www.prisma.io/docs/guides/database/developing-with-prisma-migrate/baselining resolve is needed if you have production data which cannot be reset.

npx prisma migrate resolve

marks a migration as resolved so it isn’t executed. resolve command is usually executed in production environments. Are you running into any specific issue?

Hi, thank you. No I was going through the learning curve.