P
Prisma3mo ago
Kayn

Prisma Migrate Diff coming back when it shouldn't

Our team is using Prisma as our ORM, and have a Github Action that runs
npx prisma migrate diff --exit-code --from-schema-datasource ./prisma/schema.prisma --to-migrations ./prisma/migrations --shadow-database-url
npx prisma migrate diff --exit-code --from-schema-datasource ./prisma/schema.prisma --to-migrations ./prisma/migrations --shadow-database-url
as part of our CI/CD. In a recent merge, the Diff command is flagging the follow changes [*] Changed the Project table [+] Added column assignedUsers [+] Added column tags However, as you can see in our PR, both the schema changes, and the corresponding migrations, are present. Would appreciate some help!
No description
1 Reply
Kayn
Kayn3mo ago
Very weirdly, I ran Prisma migrate diff locally, and it came up with these same diffs, as well as another change from a sperate branch that was present on my development DB. I then ran npx prisma db push, re-ran the migrate diff and it came back as clean. This indicates the state of my DB is having some sort of impact on this migrate diff command, which makes no sense since I'm checking Prisma.schema against my migrations folder, not against the current state of my DB 🤕 Bumping to see if anyone might have an answer