neon-branching

Neon Postgres branching isolates database changes per pull request by provisioning dedicated branches for testing. This enables per-PR environments for feature testing, migrations, and rapid preview workflows without touching the main database.

Managing database connection strings for PR preview environments involves retrieving per-branch connection strings after provisioning a Neon Postgres branch. This allows isolated testing and migrations specific to each pull request without affecting the main environment.

Database branching for CI/CD pipelines using serverless Postgres works by implementing branch lifecycle operations like create, delete, and reset to isolate changes. This automatically provisions per-PR databases to accelerate review and validation workflows.

You need neonctl to automate Neon Postgres branch lifecycle operations such as create, list, get, delete, reset, and set-primary. Setup guidance via neonctl and the Neon CLI configures your project to start branching for PR workflows.

You can reset or set a primary branch when testing Postgres migrations in a PR workflow using dedicated branch lifecycle operations. Resetting reverts a branch state, while setting a primary designates the main branch for your Neon serverless Postgres project.

You should not use Neon Postgres branching for pull request workflows if your project lacks CI/CD pipeline integration or does not require isolated per-PR database environments, as the branching lifecycle is specifically designed for feature testing and rapid preview validation.