GitHub

Last updated: September 2026

Connect GitHub Cloud or GitHub Enterprise Server to sync repository, pull request, and contributor activity into GitKraken Insights. Your git provider powers every PR, commit, contributor, and cycle-time metric.

Before you start: make sure you have the right access. See the prerequisites table on the Connect Your Data overview.

GitHub

In gitkraken.dev, open Insights → Settings → Data Connections.
Under Add data source, click + next to GitHub.
In GitHub, create a token (see scopes below), paste it into the field, click Validate, then Connect.

Fine-grained vs. classic token

Either works. The tradeoffs:

	Fine-grained PAT	Classic PAT
Org selection	We can’t auto-fetch your orgs — you’ll type the org name in manually	We can list your orgs in a dropdown
Best for	Tightly-scoped, single-org setups	Multi-org setups, or excluding specific orgs

We generally recommend a fine-grained token scoped to your organization.

Required permissions (read-only)

Create the token at GitHub → Settings → Developer settings → Personal access tokens. Set the Resource owner to your organization (not your personal account) so the token can see org repositories.

Fine-grained token — Repository permissions (Read-only):

Metadata — Read (selected automatically; required)
Contents — Read
Pull requests — Read

Recommended — Organization permissions (Read-only):

Members — Read — lets us match GitHub identities to people on your roster, which makes identity mapping far smoother.

If you use a classic token instead, select the repo (read) and read:org scopes.

You can edit a token’s scopes after creating it — you don’t need to regenerate it if you missed one. (Note: GitHub does not let you change a token’s expiration after creation, so set a comfortably long expiry up front.)

Once connected, GitHub data begins syncing in the background and continues over the next several hours.

GitHub Enterprise Server

Connect GitHub Enterprise Server to sync activity from a self-hosted GitHub instance.

Requirements:

The server must be reachable from GitKraken over https with a publicly-trusted certificate.
A personal access token with the repo and read:org scopes.

In Data Connections, click + next to GitHub Enterprise Server.
Optionally name the connection, then enter the Server URL — for example https://github.yourcompany.com.
Paste the GitHub Enterprise token and click Validate, then Connect.

Troubleshooting

Symptom	What’s happening	Fix
GitHub token validates, then “Connect” won’t enable	Occasional UI hiccup where re-validating clears the token	Refresh the browser, paste the token once, then Validate → Connect
No orgs to select after connecting GitHub	Expected with a fine-grained token — we can’t auto-fetch orgs	Type your GitHub org name in manually
GitHub Enterprise Server won’t validate	GitKraken can’t reach it, or its certificate isn’t publicly trusted	Confirm the Server URL is reachable over `https` from outside your network with a publicly-trusted certificate — self-signed and internal CAs won’t work

For general connection troubleshooting, see Troubleshooting setup on the Connect Your Data overview.

After connecting

Once your connection is active, continue with the remaining setup steps on the Connect Your Data overview: