Store Console

Connecting a Git Provider

The Git Connector is a single, global connection point that every product and module builds from. Configure it once under Admin → Licensing → Git Connector, then reuse it across as many release sources as you need.

Supported Providers

GitHub — Connect via the GitHub App install flow. Click Connect GitHub, authorize the app on your organization or account, and choose which repositories it can access. Webhooks are provisioned automatically.
GitLab — Works with gitlab.com or a self-hosted instance. Provide a base URL (defaults to https://gitlab.com) and a personal access token. Webhooks are provisioned automatically.
Bitbucket — Requires a workspace, a username, and an app password (generated from your Bitbucket account settings, not your login password). Webhooks are provisioned automatically.
Custom Git — For any bare git remote that doesn't fit the providers above. Only a repository URL is required — there is no API integration, so repositories cannot be browsed and webhooks are not available. Builds must be triggered manually.

Webhooks vs. Manual Builds

GitHub, GitLab, and Bitbucket connections automatically register a release webhook on each repository you connect as a release source — publishing a release or tag there triggers a build with no further action. Custom Git connections have no webhook support; use Trigger Build on the release source whenever you want to build the latest commit on the configured branch.

Multiple Connections

You can add more than one connection — for example, a GitHub connection for your main product and a self-hosted GitLab connection for an internal addon. Each release source picks exactly one connection to work from.

Disconnecting

Removing a connection stops future webhook-triggered builds for any release source that depends on it. Existing releases and builds are not affected.