# Adopting Neon branching in CI/CD pipelines: a practical story by Shepherd

DevFeed: [Adopting Neon branching in CI/CD pipelines: a practical story by Shepherd](<https://devfeed.tech/articles/adopting-neon-branching-in-ci-cd-pipelines-a-practical-story-by-shepherd-4944.md>)

Original publisher: [Read original article](<https://neon.com/blog/adopting-neon-branching-in-ci-cd-pipelines-a-practical-story-by-shepherd>)

Author: Carlota Soto

Published: 2024-07-11T16:14:05Z

Content type: article

Language: en

Sources: [Blog -- Neon Docs](<https://devfeed.tech/sources/blog-neon-docs.md>)

Topics: [CI/CD](<https://devfeed.tech/topics/cicd.md>), [GitHub Actions](<https://devfeed.tech/topics/github-actions.md>), [migration](<https://devfeed.tech/topics/migration.md>), [SQLite](<https://devfeed.tech/topics/sqlite.md>), [postgresql clusters](<https://devfeed.tech/topics/postgresql-clusters.md>), [Serverless](<https://devfeed.tech/topics/serverless.md>)

Tags: [case-studies](<https://devfeed.tech/tags/case-studies.md>), [ci-cd](<https://devfeed.tech/tags/ci-cd.md>), [clusters](<https://devfeed.tech/tags/clusters.md>), [community](<https://devfeed.tech/tags/community.md>), [github](<https://devfeed.tech/tags/github.md>), [github-actions](<https://devfeed.tech/tags/github-actions.md>), [migration](<https://devfeed.tech/tags/migration.md>), [pipelines](<https://devfeed.tech/tags/pipelines.md>), [scale](<https://devfeed.tech/tags/scale.md>), [serverless](<https://devfeed.tech/tags/serverless.md>), [sqlite](<https://devfeed.tech/tags/sqlite.md>)

## AI overview

Shepherd adopted Neon's database branching to improve CI/CD testing for its insurance pricing engine, Alchemist. After migrating from SQLite to Postgres, the team began creating ephemeral branches through GitHub Actions, reducing the need for dedicated synchronized testing databases and lowering idle infrastructure costs.

## Source excerpt

"Branching saves us both money and developer time. We no longer have to set up an actual testing database instance and make sure the data is always synced with production. We now spin up an ephemeral branch when we need to and then tear it down via the create/delete Github Action...