Product
Branching
A branch is a separate database instance that is created from an existing database. You can also create a branch from a point-in-time snapshot of a database. Branches are useful for development and testing, because they allow you to make changes to the database without affecting the original database.
How it works
- You create a new database from an existing database using the CLI or API.
- You connect to the new database using the group API token.
- Make changes to the new schema using a migration tool (optional).
- Apply the changes to the original database using a migration tool when merging using a GitHub Action (optional).
- Delete the database when you no longer need it.
Usage
You can create a new database from an existing database using the CLI or API:
Refer to the following references for more details about all arguments:
Things to know
- Database branches are completely separate from the original database. This means that you need to handle merging any schema changes or data manually using a migration tool.
- You will need to create a new token (or use a group token) to connect to the new database.
- You will need to manually delete the database branch when you no longer need it.
- Branches count towards your plan’s database quota.
CI/CD
Automating branching is useful for creating a new database for each pull request. This allows you to test changes without affecting the original database.
Here’s an example of what that might look like using the Platform API:
.github/workflows/create-database-branch.yml
Was this page helpful?