neon-postgres-branches

To create a Neon Postgres branch for testing migrations, you select a parent branch and use either the Neon MCP or CLI to execute the branch creation, optionally setting an expiration for ephemeral environments.

A normal Neon branch copies production-like data for full testing, while a schema-only branch copies just the structure without sensitive data, ensuring isolation and reproducible environments for safe testing.

Yes, you need either the Neon MCP or Neon CLI available to execute database branch creation. This Skill guides tool selection and provides the context setup and commands required for either method.

Yes, you can set an expiration on a Neon branch during creation to manage ephemeral testing environments. Post-creation guidance also includes updating connection strings and resetting from the parent branch.

The best way to reset a Neon testing branch is to use the provided post-creation guidance to reset from the parent branch, ensuring your testing environment stays synchronized with the source data structure.