Introduction to repositories

This document helps you understand the concept of repositories in BigQuery. You can use repositories to perform version control on files you use in BigQuery. BigQuery uses Git to record changes and manage file versions.

Each BigQuery repository represents a Git repository. You can use BigQuery's built-in Git capabilities, or you can connect to a third-party Git repository. Within each repository, you can create one or more workspaces to edit the code stored in the repository.

On the BigQuery page, your repositories are displayed in alphabetical order in the Repositories folder of the Explorer pane.

Third-party repositories

You can connect a BigQuery repository to a third-party Git repository if you choose. In this case, the third-party repository stores the repository code instead of BigQuery. BigQuery interacts with the third-party repository to allow you to edit and execute its contents in a BigQuery workspace. Depending on the type of repository you choose, you can connect to a third-party repository by using SSH or HTTPS.

The following table lists supported Git providers and the connection methods that are available for their repositories:

Git provider Connection method
Microsoft Azure DevOps Services SSH
Bitbucket SSH
GitHub SSH or HTTPS
GitLab SSH or HTTPS

For more information, see Connect to a third-party repository.

Service account

All BigQuery repositories are connected to the default Dataform service account. This service account is derived from your project number in the following format:

service-YOUR_PROJECT_NUMBER@gcp-sa-dataform.iam.gserviceaccount.com

Locations

You can create repositories in all BigQuery Studio locations.

Quotas

Dataform quotas apply to use of BigQuery repositories.

Pricing

You are not charged for creating, updating, or deleting a repository.

For more information on BigQuery pricing, see Pricing.

What's next