Skip to main content

⭐️ Git Integrations – Start Here

Start here to understand how LinearB connects to Git providers, what permissions are required, and which connection guide fits your environment.

Steven Silverstone
Updated by Steven Silverstone

LinearB connects to your Git provider to collect repository activity (pull requests, commits, branches, and related metadata). This data powers engineering metrics, workflow analytics, and automation features such as gitStream (when enabled).

Git integrations may require admin permissions in your Git provider. If you don’t have admin access, you may need to connect using a Personal Access Token (PAT), install an organization-level webhook, or request approval from an organization admin.
Summary
  • Pick your Git provider (GitHub, GitLab, Bitbucket, or Azure Repos) and follow the matching connection guide.
  • Cloud providers typically use OAuth when possible, with PAT as a fallback.
  • On-prem providers often require IP allowlisting and a server URL before you can authenticate.
  • After connecting, add repositories and verify the integration status in Settings → Git.
Before you begin

What you’ll need

  • LinearB role: Company Admin (recommended for setup and troubleshooting).
  • Git provider permissions: Sufficient access to authorize an app or generate a token for the repositories you want to connect.

Plan notes

  • Some providers and on-prem connections may require a paid LinearB plan.
  • gitStream availability depends on your account setup and configuration.
If you’re unsure which guide to follow, start by identifying whether your Git provider is Cloud or On-Prem (self-hosted / Data Center / Enterprise Server). That choice determines the setup flow.
Step 1 – Choose the correct connection guide

Select the guide that matches your Git provider and deployment type:

If you connect GitHub using a PAT but cannot grant webhook permissions, you may need to install an organization-level webhook to enable real-time events. See: Installing a GitHub Organization-Level Webhook .
Step 2 – Connect the provider in LinearB

All Git providers follow the same high-level path in LinearB:

  1. In LinearB, go to Settings → Company Settings.
  2. Select the Git tab.
  3. Click Add Integration.
  4. Select your provider (for example, GitHub, GitLab, Bitbucket, or Azure DevOps).
  5. Follow the on-screen prompts to authenticate (OAuth) or paste your token (PAT).
If you’re setting up an on-prem provider, complete any IP allowlisting and server URL validation steps in the provider guide before attempting to authenticate.
Step 3 – Add repositories and confirm syncing

After the integration connects, select which repositories LinearB should scan:

  1. Open Settings → Git.
  2. Find your integration under Integrations and Repositories.
  3. Click Add Repositories.
  4. Select the repositories to include, then click Save Repositories.

Once saved, LinearB begins syncing repository data. Some providers may require extra time for initial backfill, depending on repository size and history.

Repository availability depends on the permissions of the integration user/token. If a repository doesn’t appear, verify that the integration identity has access to it in your Git provider.
Managing existing Git integrations

To reauthorize a connection, update monitoring rules, add repositories, or delete an integration, see: Managing Git Integrations .

  • Reauthorize Git if authentication expires or authorization changes.
  • Monitoring Rules to control how LinearB monitors branches and PRs.
  • Delete Integration to remove a connection (and optionally its data, depending on your setup).
Troubleshooting & support

Common issues

  • Missing repositories: Confirm the integration identity is a member/admin of the repo or org, and that the repo is eligible to sync.
  • OAuth authorization blocked: Ask an org admin to approve the OAuth app or complete authorization.
  • PAT failures: Verify token scopes/permissions match the requirements in the provider guide.
  • On-prem connectivity issues: Confirm IP allowlisting, firewall rules, VPN/reverse proxy access, and server URL reachability.
  • Delayed updates: Missing webhook permissions can force polling-based sync (for example, up to ~2 hours), depending on provider setup.

If you still can’t connect, contact support@linearb.io or visit the LinearB Help Center .

How did we do?

Service Metrics

Contact