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

Project

table
[+] Added column

assignedUsers

assignedUsers

[+] Added column

tags

tags

However, as you can see in our PR, both the schema changes, and the corresponding migrations, are present.

Would appreciate some help!

Prisma•2y ago•

2 replies

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

Project

table
[+] Added column

assignedUsers

assignedUsers

[+] Added column

tags

tags

However, as you can see in our PR, both the schema changes, and the corresponding migrations, are present.

Would appreciate some help!