Set primary branch schema base on dev branch?

Support
1

I want to set primary branch schema base on dev branch, is it possible? I want to do it this way to avoid accidently destroying primary branch data. On a related note, what is the recommended workflow when working with Neon’s branching.

2

We don’t have built-in schema migration yet, but it’s on our roadmap. In the meantime, there are 3rd-party schema management options available such as Liquibase, Flyway, Prisma Migrate, and Drizzle Kit, to name a few.

We also offer GitHub Actions for creating and deleting branches, which you could use to set up a workflow with Neon branching.

Here are a couple of sample apps that you could take a look at for a potential workflow: