Git Integration - Start Here – LinearB Support

Connecting Your Git Provider to LinearB

This guide explains how Git integrations work in LinearB, what LinearB expects from each Git system, and how to connect, verify, and manage your Git providers across your organization.

Overview

LinearB connects to your Git provider to collect branches, commits, pull requests, and release information. This data powers your delivery metrics, DORA metrics, project visibility, and automation features. All Git providers connect through a secure integration that allows LinearB to read repository activity without writing code or modifying your repos.

Supported Git systems:

GitHub Cloud
GitHub Enterprise (on-prem) Server
GitLab (Cloud + Self-Managed)
Bitbucket (Cloud + Server)
Azure DevOps (Repos)

Each provider has its own authentication method and required permissions, so refer to the platform-specific guide linked below.

Before You Begin

A LinearB Admin role
Admin access to your Git provider (OAuth / PAT / App installation depending on system)
Browser access to your Git server (cloud or self-hosted)

Expected setup time: 5–15 minutes depending on provider.

Connect a Git Provider

All Git providers are connected from a single location inside LinearB.

How to Connect

Go to Settings → Integrations → Git.
Click Add Integration.
Select your Git system (GitHub, GitLab, Bitbucket, Azure DevOps).
Complete the authentication flow required by your provider.
Select the repositories you want LinearB to follow.

Platform-Specific Guides

Git Backfilling data: After initial connection, LinearB backfills 90 days of repository history. This backfill runs by default; no extra steps are required.

Git Sync time varies by provider and repository size.

Integration Management

You can manage integrations by clicking on the integration row, followed by the vertical ellipsis on the far right of that row.

Go to Settings → Git.
Under Integrations and Repositories, locate the integration you want to manage.
Click the row → then vertical ellipsis (⋮) → and select one of the following options:
1. Reauthorize Git — Refresh authentication if the token expired or permissions changed.
2. Monitoring Rules — Control which repositories, PRs, or branches LinearB monitors.
3. Delete Integration — Permanently remove the integration.

Managing Multiple Git Integrations & Removal

Disconnecting a Git Provider

You can remove a Git integration from Settings → Git → Integrations and Repositories.

Click the vertical ellipsis (⋮) on the right side of the integration card, and choose Delete Integration
Select the method for deleting the intgreation:
Remove Everything (removed integration and all date - cannot be undone).
Keep Data: Remove the intregration but but does not delete historical metrics.
Click Next, and when prompted click Delete

Multiple Git Integrations

You can connect more than one Git provider (for example, GitHub + Azure DevOps). Each connection appears separately in the integrations list. This feature is not enabled by default. To enable multi-integration, please contact support

Next Steps

Map repos to teams for correct metric attribution
Enable real-time activity via Slack or Teams
Configure DORA Metrics
Connect your Project Management tool

Repository Management

After connecting, LinearB displays all accessible repositories. Repositories with a checkmark are being scanned; uncheck any repo you do not want LinearB to analyze.

Adding or Updating Repositories

To add repositories to an existing integration:

Click Add Repositories nest to the integrtion name.
In the Select repositories for your organization window, choose which repositories LinearB should scan
Filter by visability (private, internal, all)
Use the search bar to find a specific repository
Select all available repositories if you want ot include all active repos.
When finished, click Save Repositories

How LinearB Uses Your Git Data

Branches, Commits & PRs

LinearB reads branch creation, commits, branch merges, and pull request metadata from your Git provider. This activity populates:

Cycle Time
Pickup Time
Review Time
Time to Merge
PR Size
Deployment Frequency

Repository Metadata

Repository settings, users, and permissions determine which branches are visible, which contributors map to which users, and which automations can run.

Webhooks (GitHub / GitLab Cloud)

Certain providers use webhooks for real-time updates. For GitHub organization accounts, LinearB supports an organization-level webhook that sends push, PR, tag, and branch events to LinearB.

Webhook events are required for faster synchronization but do not grant write access. All webhook payloads use read-only scopes, according to provider docs.

Verify Your Git Integration

How to Confirm Your Connection is Working

Repositories appear in Settings → Integrations → Git.
New commits appear in Git Activity.
Pull requests appear in Delivery → PRs.
Branches move through Coding → Review → Merge stages.

Troubleshooting

Problem	Likely Cause	Fix
Missing repositories	Insufficient permission scopes or token missing repo access	Update OAuth or PAT scopes; reconnect and reauthorize
No pull requests syncing	PR access not granted or provider limits on app permissions	Verify the app/token has PR read access
Self-hosted server not connecting	Firewall or private network issue (GitHub Enterprise, GitLab Server, Bitbucket Server)	Ensure LinearB can reach the server URL from the internet
Webhook not firing	Webhook not installed or disabled in Git provider	Reinstall the webhook following the provider guide
Authentication fails on reconnect	Expired token or revoked authorization	Create a new PAT or re-authenticate via OAuth