This feature is available on our Business and Enterprise plans
Please contact us if you're interested in learning more or trialing the integration
Whether you’re looking to build pipelines from a git repository 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 or GitLab sync. Once you connect a repo to PopSQL, if you make a change in PopSQL, it gets pushed to GitHub or GitLab 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 git integration, 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 or GitLab, clone the repo in a free code editor tool like VS Code, do a global bulk find and replace, push to GitHub or GitLab, and the changes will be reflected in all the relevant queries in PopSQL -- saving hours of time and eliminating the risk of inaccurate reports.
Q: What from PopSQL gets pushed into Git?
A: Only shared team queries and the folders they're in get synced into Git.
Q: How often do commits happen in Git?
A: Commits occur with every auto-save that happens in PopSQL.
Q: Can queries be created directly in the Git repo?
A: No, queries need to be created first in PopSQL, then any changes can be made either in PopSQL or Git.
Q: How can I ensure that major changes I make in GitHub/Gitlab avoid conflicts in PopSQL?
A: Since PopSQL <> Git is a two-way sync it's best to make changes at a time when other users are not making changes in PopSQL to ensure the smoothest update.
Updated 5 months ago