Administration

Connecting Git Providers

Driver connects to your Git provider to access repositories and keep documentation current. When you push code changes, webhooks notify Driver to update the affected codebase documentation automatically.

Note: If your Git provider restricts inbound connections by IP, see IP Allowlist for the addresses to allowlist.

Note: You need Org Admin access to your Driver organization and admin access to your Git provider (GitHub org, GitLab group, Bitbucket workspace, or Azure DevOps project) to set up integrations.

Supported Providers

  • GitHub
  • GitLab (Cloud and Self-Managed)
  • Bitbucket Cloud
  • Bitbucket Data Center
  • Azure DevOps

General Setup Flow

For GitHub, the flow is simplified: install the Driver GitHub App, authorize access, and select repositories.

For all other providers, the flow is:

  1. Create a connection — Name your instance, workspace, or organization.
  2. Add an access token — Generate a token in your Git provider and paste it into Driver.
  3. Set up webhooks — GitHub and Bitbucket Data Center set up webhooks automatically. For GitLab, Bitbucket Cloud, and Azure DevOps, configure webhooks manually.
  4. Select repositories — Choose the repositories you want Driver to generate context for.

Provider Guides

GitHub

Install the Driver GitHub App. Webhooks configured automatically.

GitLab

Connect with a Group Access Token. Cloud and Self-Managed.

Bitbucket Cloud

Connect with an Access Token.

Bitbucket Data Center

Connect with an Access Token. Automatic webhooks.

Azure DevOps

Connect with a Personal Access Token.