GitKraken Client and GitHub Enterprise Server Pull‑Request Integration Interoperability

Question

Goal: Verify that GitKraken Client’s pull‑request integration (listing, reviewing, and merging) functions with the same capability set when connected to a self‑hosted GitHub Enterprise Server instance as it does with GitHub.com.

Constraints: The integration relies on OAuth or personal‑access‑token flows, and GitKraken’s release notes indicate that authentication methods and supported API endpoints have evolved across versions, which may cause silent failures or reduced functionality against newer GHE releases. Documentation does not explicitly state feature parity for enterprise installations.

Questions: Does GitKraken support OAuth‑based authentication to GHE, and if not, what token scopes are required? Are pull‑request review and merge actions available in the client when connected to GHE, or are they limited to read‑only listing? Are there any known version‑specific limitations that prevent full interoperability?

Tasadduq Burney · Answer

Direct answer
GitKraken can authenticate to a self‑hosted GitHub Enterprise Server (GHE) using either OAuth (if a GitHub OAuth App is registered on the enterprise and the client is pointed at the instance URL) or a personal‑access‑token (PAT). When the token (or OAuth token) has the required scopes, the client exposes the full pull‑request workflow—list, comment, approve, request changes, and merge—just as it does with GitHub.com.
Confirmed facts

OAuth support depends on having a registered OAuth App on the GHE and enabling the OAuth option in GitKraken’s Accounts → GitHub Enterprise settings.
For PR operations the token must include the repo scope (full control of private repositories). When using OAuth, additional scopes such as admin:repo_hook, read:org, user:email, workflow and notifications are also required.
With the correct scopes, GitKraken’s UI shows the merge button and review controls for PRs on GHE.
Known version‑specific limits: GitKraken releases prior to v7.0 (early 2020) have unreliable OAuth flows for GHE, and GHE releases before version 2.12 do not expose the merge pull‑request endpoint, which disables the merge button in the client.

Steps to verify

In GitKraken, open Help → Accounts → GitHub Enterprise. If you see an “OAuth” option, try the authorization flow; success indicates OAuth is usable.
Create a test PAT with only the repo scope (add admin:repo_hook if you need to manage webhooks). Use that PAT to add an account in GitKraken.
Open a test repository, create a PR, and confirm you can list, comment, approve/request changes, and click the merge button.
Optionally run curl -H "Authorization: token $TOKEN" https:///api/v3/user/repos; a 200 response confirms the token works against the API.
Compare the merge button state in GitKraken with the same PR on the web UI; if both are enabled, full interoperability is present.

Missing diagnostic detail
To be certain that the merge action is available, we need to know the version of your GitHub Enterprise Server. If it is older than 2.12, the merge endpoint is missing and the merge button will be disabled regardless of token scopes.

GitKraken Client and GitHub Enterprise Server Pull‑Request Integration Interoperability

1 answer

Direct answer

Confirmed facts

Steps to verify

Missing diagnostic detail

Your perspective belongs here.

0 question comments