GitKraken Desktop to GitHub/GitLab: Cancel behavior for long-running clone and fetch

GitKraken Desktop to GitHub or GitLab: Cancel behavior for long-running clone and fetch

The goal is to determine whether canceling an in-progress Git clone or fetch in GitKraken reliably terminates the underlying Git process and leaves no partial packfiles or unintended working-tree changes. Public documentation does not appear to define a single GitKraken-controlled operation timeout; transfers instead depend on transport settings such as http.timeout and low-speed-limit, and behavior may differ between HTTPS and SSH remotes and across operating systems.

OAuth or personal access token expiry is a separate concern from network transfer timeouts, and GitKraken Enterprise or proxy configurations may add server-side deadlines. The installed release should be treated as the version boundary for any observed behavior.

Does GitKraken guarantee process termination on cancel for both HTTPS and SSH remotes? Are partial objects cleaned automatically after cancellation? Is there a supported client-side timeout setting that applies uniformly to clone, fetch, and pull?