Skip to main content

Phase 1 — Confirm Git Connection

In this phase, confirm that your Git provider is connected and that LinearB is successfully ingesting repository activity. Git data powers nearly every feature in LinearB Essentials, including dashbo…

Steven Silverstone
Updated by Steven Silverstone

In this phase, confirm that your Git provider is connected and that LinearB is successfully ingesting repository activity. Git data powers nearly every feature in LinearB Essentials, including dashboards, AI insights, and gitStream automations.

Estimated time: 5–10 minutes

Step 1 — Confirm Your Git Provider

LinearB Essentials requires a Git provider to collect commit activity and pull request data. In most cases, your Git provider is connected during your first login to LinearB.

  1. Go to Settings → Integrations → Git.
  2. Confirm your Git provider is listed (for example: GitHub, GitLab, Bitbucket, or Azure DevOps).
  3. If multiple providers appear, confirm the correct one is active.

Expected result:

  • Your Git provider is visible in the Git integrations page
  • The connection status shows as Connected

Step 2 — Confirm Repository Selection

After connecting your Git provider, LinearB must be allowed to access the repositories you want to track.

  1. In Settings → Integrations → Git, review the repository list.
  2. Confirm the repositories you want LinearB to analyze are selected.
  3. If needed, enable additional repositories.

Expected result:

  • The repositories you care about are visible in the list
  • The correct repositories are selected for analysis
Tip
Start with a small number of repositories for your initial rollout. Once the setup is verified, you can expand access to additional repositories.

Step 3 — Confirm Git Data Is Syncing

Once repositories are selected, LinearB begins ingesting commit and pull request activity. This data powers dashboards, AI insights, and automation rules.

  1. Go to Dashboards.
  2. Select any team or repository dashboard.
  3. Review recent activity.

Expected result:

  • Recent pull requests appear
  • Commit activity appears for developers
  • Repository names match your Git provider
If no data appears
Confirm the correct repositories are selected and verify the Git integration connection. If the issue persists, reconnect the Git integration or contact LinearB support.

Once Git is connected, many organizations configure exclusions to improve data accuracy. These settings are optional during initial setup and can be configured later if needed.

  • Branch exclusions — exclude non-production branches such as test or sandbox.
  • File exclusions — exclude generated or non-code files from PR metrics.
  • Draft pull request rules — ensure unfinished work does not distort Cycle Time or Review Time.
  • Bot exclusions — prevent automation accounts from appearing as contributors.

You can configure these settings later under:

  • Company Settings → Advanced
  • Settings → Git (repository-level overrides)

What Success Looks Like

  • Your Git provider is connected
  • The correct repositories are selected
  • Pull requests and commits appear in dashboards
Phase 1 complete.

Once Git activity is visible in LinearB, continue to configuring users and access.

Continue to Phase 2 — Configure Users & Access →

How did we do?

Phase 2 — Configure Users & Access

Contact