Skip to main content
Table of Contents

Integration Guide - GitHub Enterprise Server (on-prem)

Use this guide to connect your GitHub Enterprise Server (on-prem) instance to LinearB. You’ll add your server URL, authenticate with a Classic or Fine-Grained token, and select the repositories you w…

heather.hazell
Updated by heather.hazell

Use this guide to connect your GitHub Enterprise Server (on-prem) instance to LinearB. You’ll add your server URL, authenticate with a Classic or Fine-Grained token, and select the repositories you want to sync for accurate Git-based metrics and visibility.

Time Required: 5–10 minutes
Difficulty: Easy

Overview

LinearB’s paid plans support connecting on-prem Git servers, including GitHub Enterprise Server. This integration is set up from LinearB using your GitHub Server URL and an access token (Classic or Fine-Grained).

If your network is private, you must allowlist LinearB’s IP addresses so LinearB can reach your GitHub Enterprise Server instance.

Before You Begin

  • LinearB Admin access.
  • Admin access to your GitHub Enterprise Server instance.
  • Your GitHub Server HTTPS URL.
  • Ability to create a GitHub Server access token.

Setup at a glance

You’ll need:

  • Your GitHub Enterprise Server HTTPS URL
  • A Classic or Fine-Grained token with the required scopes
  • Network access for LinearB:
    • If your server is public, you can skip allowlisting.
    • If your server is private, you’ll need to allowlist LinearB IPs or use a reverse proxy for VPN setups.

What you’ll do:

  1. Select GitHub Enterprise Server in LinearB.
  2. Confirm network access (allowlist if needed).
  3. Enter your server URL.
  4. Choose token type and confirm scopes.
  5. Create or reuse a token.
  6. Connect and select repositories.

Steps

1. Select GitHub Enterprise Server as your Git provider
  1. In LinearB, go to Settings → Company Settings → Git.
  2. Click Add Integration.
  3. Select GitHub Enterprise Server.
2. Allow LinearB access (private networks only)

If your GitHub Enterprise Server instance is accessible from the public internet, you can skip this step.

For private networks, allowlist LinearB’s public IP addresses in your firewall:

  • 52.15.80.85
  • 54.241.87.26
  • 54.193.121.186
  • 18.118.232.229

For networks behind a VPN, use a reverse proxy that allows LinearB-specific access to your GitHub Enterprise Server.

3. Insert your GitHub Server URL
  1. Enter your GitHub Server URL (for example, https://github.yourdomain.com).
  2. LinearB will check connectivity.
  3. Click Continue.
4. Connect with a Classic or Fine-Grained token

When prompted, choose your authentication method.

If you use a Classic token, ensure these scopes are selected:

  • read:repo_hook
  • repo
  • write:repo_hook
  • user:email
  • read:discussion
  • read:org
  • read:user
5. Create a Personal Access Token (if needed)

Already have a token? If it matches the required scopes, you can skip token creation and continue to the connection step.

Create a token in GitHub Enterprise Server and enable the access scopes listed in the current guide for your server version.

The guide additionally calls out these scopes during PAT creation:

  • repo
  • admin:org
  • read:enterprise
  • admin:repo_hook

Copy the token immediately. You will use it in LinearB.

6. Validate, connect, and select repositories
  1. Paste your token into LinearB.
  2. LinearB will validate the token.
  3. Select the repositories you want LinearB to follow.

You can update repository selection later from the Git integration settings.

Verify

Confirm the integration is working
  • Go to Settings → Company Settings → Git.
  • Confirm GitHub Enterprise Server shows as Connected.
  • Open the integration to confirm your selected repositories are listed.
  • Repository activity should begin appearing in relevant Git-based views.

Troubleshooting

Problem Possible cause How to fix
LinearB cannot connect to GitHub Server Firewall/VPN restrictions or missing allowlisted IPs Allowlist LinearB IPs or configure a reverse proxy for LinearB access.
Missing repositories Token permissions or repo selection Verify token scopes and confirm the repos are selected in LinearB.
Real-time updates not working Webhook permissions missing Ensure the token includes the webhook scopes listed in the guide.

FAQs

Does LinearB require write permissions?
Only for webhook management when applicable. LinearB does not write to your source code.

Can I connect multiple GitHub Enterprise Server instances?
Yes. Add additional integrations from the Git settings.

You’ve successfully connected GitHub Enterprise Server to LinearB.

Next Steps

How did we do?

Integration Guide - GitHub Cloud

Integration Guide - GitLab (Cloud + Self-Managed)

Contact