GitKraken Client and GitHub Enterprise Server Pull‑Request Integration Interoperability

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?