Git Integration

Connect your Git repositories to import and synchronize data contracts with Entropy Data.

Entropy Data supports integration with GitHub, GitLab, Azure DevOps, and Bitbucket Cloud, allowing you to leverage your existing Git workflows and keep your data contracts in sync between your code repositories and the platform.

GitHub

Connect your GitHub repositories to import and synchronize data contracts. The integration supports both fine-grained and classic personal access tokens.

Key Features:

Import data contracts from GitHub repositories
Automatic synchronization between Git and Entropy Data
Pull updates from GitHub to Entropy Data
Push changes from Entropy Data back to GitHub
Support for both fine-grained and classic tokens

Follow the Connect Git Repository Guide for detailed setup instructions and GitHub token creation.

GitLab

Connect your GitLab repositories to import and synchronize data contracts. The integration uses GitLab personal access tokens for authentication.

Key Features:

Import data contracts from GitLab repositories
Automatic synchronization between Git and Entropy Data
Pull updates from GitLab to Entropy Data
Push changes from Entropy Data back to GitLab
Support for self-hosted GitLab instances

Follow the Connect Git Repository Guide for detailed setup instructions and GitLab token creation.

Azure DevOps

Connect your Azure DevOps repositories to import and synchronize data contracts. The integration uses Azure DevOps personal access tokens for authentication.

Key Features:

Import data contracts from Azure DevOps repositories
Synchronization between Git and Entropy Data
Pull updates from Azure DevOps to Entropy Data
Push changes from Entropy Data back to Azure DevOps
Create pull requests directly from Entropy Data
Support for both Azure DevOps Services (cloud) and Azure DevOps Server (self-hosted)

Additional Hint: Due to restrictions in the Azure DevOps APIs, all repositories for all projects in an organization are loaded as hints for repository creation. If this includes too many projects, it can happen that no repository hints are shown. In this case you are able to enter the repository URL without the list of hints. Just copy or type it into the input field.

Follow the Connect Git Repository Guide for detailed setup instructions and Azure DevOps token creation.

Bitbucket Cloud

Connect your Bitbucket Cloud repositories to import and synchronize data contracts. The integration supports Bitbucket API tokens (recommended) as well as access tokens for authentication.

Key Features:

Import data contracts from Bitbucket Cloud repositories
Automatic synchronization between Git and Entropy Data
Pull updates from Bitbucket to Entropy Data
Push changes from Entropy Data back to Bitbucket
Create pull requests directly from Entropy Data for protected branches
Branch protection detection

Authentication: For user-based authentication on Bitbucket Cloud we recommend API tokens linked to your Atlassian account, used together with your Atlassian account email as the username. Atlassian is phasing out App Passwords in favour of API tokens.

The following token types are supported:

API token (recommended for user-based auth). Atlassian API token used over HTTP Basic, with your Atlassian account email as the username. Bitbucket App Passwords are still accepted in the same field but have been deprecated by Atlassian and will be permanently disabled on Jun 9, 2026 and removed on Jul 28, 2026; prefer an API token.
Access token (for service / automation auth). Repository, project, or workspace access tokens with read and write permissions for repositories and pull requests, sent as a Bearer token.

Only Bitbucket Cloud (bitbucket.org) is supported. Self-hosted Bitbucket Data Center is not supported at this time.

With an Access Token, the repository picker cannot list repositories — Access Tokens are scoped to a single repository, project, or workspace and have no user identity, so the workspace-discovery API used to populate the dropdown returns no results. Enter the repository URL manually instead. Use an API token if you want the dropdown to populate.

Follow the Connect Git Repository Guide for detailed setup instructions.

Auto Pull from Git

Automatically pull changes from your Git repository into Entropy Data whenever commits are pushed, so the platform stays in sync with Git without manual imports. This is the inbound direction of Git synchronization; the outbound direction (Entropy Data → Git) is handled by Auto Push.

Auto Pull uses a webhook. Each connected repository has its own webhook URL, shown in the Auto Sync Git to Entropy Data section of the Git connection dialog. Configure that URL as a webhook in your Git provider, and every push to the configured branch triggers Entropy Data to pull the latest file.

Key Features:

Works with GitHub, GitLab, Azure DevOps, and Bitbucket Cloud — the webhook is provider-agnostic and needs no payload configuration or signing secret.
The webhook URL carries a secure token that identifies the repository, branch, and provider, so any provider's push event triggers a pull.
A single webhook URL updates every data contract and data product connected to the same repository, branch, and provider.

Requirements:

Git credentials must be available at the organization level (or on the team, or pinned to the connection). Auto Pull runs without a signed-in user, so user-level credentials are not used — without an organization or team credential, nothing is synced.
The webhook URL depends on the provider, host, repository URL, and branch. Changing any of these regenerates the URL, so update the webhook in your provider afterwards.

Setup:

Open the Git connection dialog for a data contract or data product and select the provider, repository, and branch.
Copy the generated URL from the Auto Sync Git to Entropy Data section.
Add a webhook for push events in your Git provider, pointing to that URL:
- GitHub
- GitLab
- Azure DevOps
- Bitbucket
Push a commit — Entropy Data pulls the updated file automatically.

The webhook URL contains a secret token: anyone with the URL can trigger a pull for that repository. Treat it like a credential and add it only to your Git provider's webhook settings.

Auto Push to Git

Automatically push changes made in Entropy Data back to your Git repository whenever a data contract or data product is saved, keeping the repository in sync with the platform. This is the outbound direction of Git synchronization; the inbound direction (Git → Entropy Data) is handled by Auto Pull.

Auto Push is configured per connection in the Auto Sync Entropy Data to Git section of the Git connection dialog, and its default can be set organization-wide in Git settings.

Modes:

Default — use the organization-level Auto Push setting.
Disabled — never push automatically; changes stay in Entropy Data until pushed manually.
Auto-sync via MR/PR — on save, push the change to a new branch and open a merge/pull request instead of committing directly to the target branch. Suited to protected branches and review workflows.
Auto-sync directly to branch — on save, commit and push straight to the target branch, with no merge/pull request.

Use "Auto-sync directly to branch" with care: every save is committed straight to the target branch with no review step, so mistakes propagate immediately and can overwrite others' work. Prefer "Auto-sync via MR/PR" for shared or protected branches, and reserve direct-to-branch syncing for personal or short-lived branches where unreviewed writes are acceptable.

Requirements:

The connection's Git credentials must have write access to the repository (and permission to open merge/pull requests when using the MR/PR mode).
The initial push must be performed manually — Auto Push keeps an already-synced file up to date, it does not create the file on first connect.

On protected branches a direct push is rejected by the provider. Use the MR/PR mode (or the manual "Create pull/merge request" option) so changes land through a reviewed merge/pull request.