

By connecting your GitHub repository to superQuery, you’ll have effectively transformed your repo into a query library.





How does it work?

Every time you execute a query in superQuery and there is a change in the SQL, your query will automatically get committed to your selected GitHub repository.

This also applies to BigQuery views. Provided that your colleagues are connected to the same repository, all changes made to views will be committed to GitHub. From there, you’ll see the history of revisions made to that view and which colleague made the change.



How are queries organized?

If there are multiple users connected to the same repository, each user will have their own folder in the repo.

Your queries are catalogued under a hierarchy of Boards > Query Tabs , making your library easy to navigate (as long as you give your boards & tabs good names).

As a result, there’s no need to think up your own naming convention. Everything is done for you auto-magically so you can focus on data analysis.