Version control introduction

Tinybird’s Git integration transforms data pipeline management, aligning it with established software development practices. This ensures each Tinybird Release corresponds to a specific Git commit, offering a robust, version-controlled environment for your real-time data deployments.

Why use version control?

Version control, a standard in software development, is now integral to building real-time data products with Tinybird. If your Workspace uses Tinybird’s integration with Git, it means you can build real-time data products like you build any software - not just benefiting from version control, but also isolated environments, CI/CD, and testing too.

This approach allows you to treat and manage your real-time data in the same way you manage your code. You can take your existing software engineering knowledge and apply the same principles to real-time data products.

When managing your Tinybird projects with version control, you can also:

  • Sync Tinybird Releases with your Git commits.

  • Deploy semantically-versioned Data Sources, Pipes, and API Endpoints as code.

  • Deploy Releases in preview to test how they’ll impact your production Release.

  • Have a semantically versioned Release history, so you can roll back if needed.

  • Use branches to attach production data to non-production branches, and test your data pipelines safely with real data.

If you’re familiar with version control already, it should make testing, merging, and deploying your Tinybird data projects a familiar process.

In the same way software engineering teams have work agreements to use version control, code reviews, quality assurance and testing strategies, and continuous deployment, data teams can use Tinybird in the same way, to enforce those same agreements.

You don’t need to do anything to activate version control - all new Workspaces have it enabled.

How to get started