About Git Repositories

You can use an external Git repository in a public Git account to store your integration projects or packages. A project or package corresponds to a folder or a container for organizing your integrations.

The external Git repositories that are supported are as follows.

  • GitHub
  • Gitlab
  • Bitbucket
  • Azure Repos
Note:
  • Git support for projects is available upon request only for the Enterprise Plus tier.
  • Only cloud-based Azure Repos are supported; self-hosted Azure Repos are not supported.

Key Points to Remember when Using Git Repositories

  • A Git account is needed to store your project files in a Git repository.
  • A Git repository cannot be linked to an existing project; only new projects can be linked to a Git repository.
  • The Git repository of a project cannot be changed after the project is linked to a Git repository. Also, existing projects cannot be linked to a Git repository; only new projects can be linked.
  • A single Git repository cannot be associated with multiple projects.
  • You can have one account per Git host.
  • Workflows and flow services are not currently included in version control. Only deploy anywhere flow services and related assets are saved in your Git repository.

Overview - Storing Project Files in Git

The basic flow to store your project files in a Git repository is as follows.

  1. Configure your Git account information to securely connect to your private Git repositories from your tenant, facilitating the storage of your project assets. You can configure your Git account details on the Version Control page. For more information, see Configuring Git Accounts.
  2. Link the Git account details to a project to store the project assets. For more information, see Linking Projects to a Git Repository.
After successfully linking to a project, the project files are stored in the configured Git repository.
Note: To view, update, or delete any of the configured Git accounts, see Viewing Configured Git Accounts.