Introducing PopSQL + dbt. The first SQL editor with built-in dbt support.Read more →

How to connect a GitHub repository

Whether you’re looking to build pipelines from GitHub to dbt, Tableau, Looker, etc. or looking for an additional layer of data governance, on top of PopSQL’s in-app version history, PopSQL has you covered with our two-way GitHub sync. Once you connect a repo to PopSQL, if you make a change in PopSQL, it gets pushed to GitHub and vice versa.

The benefit of this integration is that it gives you more control of your data. For example, imagine you have thousands of queries and need to swap a table name due to a schema change. Without GitHub, your end users would have to manually make these changes one by one. However, with our two-way sync, you can persist all your PopSQL queries in GitHub, clone the repo in a free code editor tool like VS Code, do a global bulk find and replace, push to GitHub, and the changes will be reflected in all the relevant queries in PopSQL -- saving hours of time and eliminating the risk of inaccurate reports.

Here’s how to get started once you have GitHub enabled

This feature is available in our Enterprise plan. Please contact us if you're interested in learning more or trialing the integration.

Step 1: Create a new GitHub repo, e.g.

Step 2: Visit your PopSQL settings page and click the button to connect GitHub.


Step 3: Authorize PopSQL and select the repo you just made.


Step 4: Click to install and you’re all set!

Currently, your SQL files will transfer to GitHub as flat files. Coming soon, we’ll be bringing the same folder structure in PopSQL to GitHub.

Ready for a modern SQL editor?