Does GitKraken support GitHub fine‑grained personal access tokens?

The goal is to verify whether GitKraken can authenticate to GitHub using a fine‑grained personal access token (PAT) and correctly enforce the token’s scoped permissions for common repository actions. GitKraken’s documentation mentions OAuth and legacy PAT support but does not explicitly state compatibility with GitHub’s fine‑grained PAT model, which introduces repository‑specific scopes. Because the behavior may differ across GitKraken versions and the token scope syntax is relatively new, it is unclear if the client accepts the token, prompts for missing scopes, or silently fails when an operation exceeds the granted permissions.

• Does GitKraken accept a fine‑grained PAT that includes only the repository‑read scope?
• When attempting a push or branch creation with a token lacking the required write scope, does GitKraken display a scope‑related error or prompt for additional authorization?
• Are any scope‑validation messages logged in the application console or debug output when a fine‑grained PAT is used?