Skip to main content

​
Overview

Coalesce Quality reads your Git repositories to show how the code behind your data changes. It works with dbt, LookML, SQLMesh, Coalesce Transform, custom entities and any other code you keep in Git. With a Git integration connected, you can:
  • See model changes in the UI, with optional diffs.
  • See recent commits for failing models in alerts.
  • Link code changes to the data assets they affect.

​
Supported Git providers

Coalesce Quality works with any Git provider that supports SSH access. All providers use the same Git integration form and a read-only SSH key. Pick your provider for the steps to add the key: For GitHub you can also install the Coalesce Quality GitHub App instead of adding a deploy key. See GitHub.

​
Integration requirements

  • Coalesce Quality must be able to reach your Git server over the internet. You can limit access to the egress IP addresses for your region, see IP Whitelist.
  • The repository must be reachable over SSH, usually on port 22. HTTPS clone URLs are not supported.
  • The Git server must accept an SSH deploy key, or an SSH key on a service account. The key needs read-only access to the repository.
Setting up a code integration has two steps:
  1. Create the Git integration in Coalesce Quality.
  2. Add its public SSH key to your Git provider.

​
Configuring the Integration

All Git providers use the same integration form. Navigate to Settings > Add integration > Git to get started.

​
Integration Name

Provide a descriptive name for your integration. Examples:
  • Production Analytics Repo
  • Data Platform GitHub
  • Bitbucket Staging

​
Repository URL (SSH)

Enter the SSH URL of your Git repository. Format: git@hostname:organization/repository.git Examples:
  • GitHub: git@github.com:myorg/analytics.git
  • GitLab: git@gitlab.com:myorg/data-platform.git
  • Bitbucket: git@bitbucket.org:myworkspace/dbt-project.git
Only SSH URLs are supported. HTTPS URLs will not work.

​
Branches to Analyse

Specify which branches to analyze.
  • Default: Leave empty to automatically use main or master
  • Custom: Enter specific branch names (e.g., develop, staging, production)

​
Path to Analyse

Define the directory path where your source code is located.
  • Default: Leave empty to analyze the entire repository
  • Custom: Enter a subdirectory path (e.g., analytics/, transform/dbt/)
In most cases, analyzing the entire repository (default) is recommended.

​
Commit URL Format (Optional)

For GitHub, GitLab, Bitbucket and Azure DevOps, the correct commit URL format is determined automatically. For custom or self-hosted instances, you may need to specify it manually. Available Placeholders:
  • {owner} - Repository owner or organization. For a host that is not GitHub.com, GitLab.com, Bitbucket.org or Azure DevOps, this is the host name.
  • {name} - Repository name. For a host that is not GitHub.com, GitLab.com, Bitbucket.org or Azure DevOps, this is the full repository path.
  • {hash} - Commit hash
  • {branch} - Branch name
  • {web_url} - Repository web URL
  • {provider} - Git provider (github, gitlab, bitbucket, azuredevops)
Format Examples:
  • GitHub: https://github.com/{owner}/{name}/commit/{hash}
  • GitLab: https://gitlab.com/{owner}/{name}/-/commit/{hash}
  • Bitbucket: https://bitbucket.org/{owner}/{name}/commits/{hash}
  • Self-hosted: {web_url}/commit/{hash}. This is the default for hosts other than GitHub, GitLab, Bitbucket and Azure DevOps.
{web_url} is built from the SSH URL as https://<host>/<path>. If your Git server uses a different web address, write the full commit URL for your repository and use only {hash}, for example https://git.example.com/data/analytics/-/commit/{hash}.

​
Data Collection

Store commit diff: Enable this option (checked by default) to collect and display actual code changes in the Code & Changes screen.

​
Create and Get Public Key

Click Create. Coalesce Quality generates an SSH key pair and opens the integration page, which shows the Public key. Copy it and add it to your Git provider as a read-only deploy key. You can come back to the integration page at any time to copy the key again.

​
Access permissions

You need admin access to the repository to add a deploy key. The deploy key itself gives read-only access to that one repository. It cannot change your code and gives no access to the rest of your organization.

​
Adding Deploy Keys to Your Git Provider

After you copy the public SSH key, add it to your Git provider:

GitHub

Add deploy key to GitHub repositories

GitLab

Add deploy key to GitLab projects

Bitbucket

Add access key to Bitbucket repositories

Azure DevOps

Add SSH key to Azure DevOps Repos

Other Providers

Self-hosted and other SSH-based Git