Read writing from GitKraken on Medium. GitKraken, the downright luxurious Git GUI client for Windows, Mac and Linux. GitKraken makes Git commands and processes easy, fast, and intuitive. GitKraken takes advantage of the explosive growth in Git popularity among development and DevOps teams, and the growing need to support developers with less Git experience. GitKraken's ease of use helps it reach users beyond heavy-hitter Git experts. As of Visual Studio 2017, SSH can be used to connect to Azure DevOps Git repos. How SSH key authentication works SSH public key authentication works with an asymmetric pair of generated encryption keys. The public key is shared with Azure DevOps and used to verify the initial ssh connection.

• By default, GitKraken connects to one integration at a time. However, with GitKraken Pro ‘s multiple profile support, you can easily switch between profiles that each have their own associated GitHub and BitBucket accounts. If you have PRO, set up profiles to configure a GitHub, GitLab, Bitbucket, or Azure DevOps account for each profile.
• GitKraken allows you to authenticate with GitHub, GitLab, Bitbucket, and Azure DevOps (previously VSTS), which will help you find repos when cloning or adding your remotes.

GitKraken can connect to repositories hosted on most services (like TFS, AWS CodeCommit, Google Cloud Source Repositories, custom service, etc), over HTTPS or SSH.

HTTPS

The most common and default way to interact with a remote repository, HTTPS configuration will always require your Git username and password credentials.

To clone a remote repository over HTTPS, first navigate to your hosting service and copy the HTTPS link. The URL should be formatted like this:

Then go to GitKraken and clone the project through File Clone.

Paste the URL, hit , and then open the repo in GitKraken.

By default when cloning a repo using HTTPS, your remote tracking at origin will be set using this format.

SSH

Before you can clone a repo over SSH, you must first set up your SSH keys in GitKraken.

Navigate to Preferences SSH.

Here you may choose an SSH key pair by browsing your file system, or let GitKraken generate a key for you (recommended). Make sure that you copy your public SSH key and paste it into your remote hosting service!

Once your keys are set up, you are ready to clone.

Clone over SSH

To clone a remote repository over SSH, first navigate to your hosting service and copy the SSH link.

Then go to GitKraken and clone the project through File Clone.

Paste the URL, hit , and then open the repo in GitKraken.

Supported SSH formats

The standard protocol can be entered as a remote in one of following formats:

or

where

• {host} can be example.com
• {user} is the username (git by default)
• {repo} is myrepository.git

Note:{repo} usually has an owner like a user or organization where the repository is located on which ssh://{user}@{host}/{owner}/{repo} would be used.

For example, the original HTTPS URL in SSH is formulated as

By default when cloning a repo using SSH, your remote tracking at origin will be set using this format.

Custom SSH ports

To use a custom SSH port, you need to use the ssh:// format for your SSH URL.

Local SSH Agent

'Never send a human to do a machine's job.'

A local SSH agent handles key communication with your remote host, without needing a passphrase.

With SSH, it's not uncommon when working with many projects, and separate profiles that you need different credentials.

While you can specify a single SSH key pair as a default, and even have dedicated defaults per profile, it may be preferable to check Use local SSH agent and have the keys managed externally.

This way, provided your keys are loaded, every action requiring a chat with your known hosts can manage providing l33tp@$$..&3 for success without your keyboard involved.

100% of the time, it works every time.

I'm having an SSH issue.

Well if it's not working 100% of the time, the most common issues are:

• SSH-agent on Windows — GitKraken currently only supports Pageant for the SSH agent for Windows.
• You can download PuTTY and Pageant from their page here.
• Misconfigured SSH settings — remote URL format
• Check in Preferences Authentication to confirm that your SSH settings are correct.
• Edit remotes in the left ref panel to ensure push and pull urls are set and in the correct format
• Expected use of SSH config — GitKraken does not currently respect your SSH config and cannot make use of any remote server nicknames or identities.
• You can either load your SSH key directly into GitKraken or use your system’s SSH agent to authenticate with your remote.

Forget all

You may tell GitKraken to forget all usernames and passwords from Preferences Authentication:

Use this if you need the app to prompt for username or password for remote actions like push or pull.

Proxy configuration

GitKraken supports proxies for Windows, OSX, and Linux. GitKraken should recognize your proxy settings by default, however please review the additional instructions below if you are using an authenticated proxy such as basic, NTLM, Negotiate, or Digest.

Windows

For Windows users, your Windows machine will prompt for your proxy credentials on GitKraken’s behalf. Enter the credentials to complete the proxy configuration with GitKraken.

OSX

If you’re using an authenticated proxy on OSX, GitKraken will directly ask for the proxy credentials. Enter the credentials to complete the proxy configuration with GitKraken.

Linux

If you are using an authenticated proxy on Linux, Gitkraken will directly ask for the proxy credentials. Additionally, you will need to run GitKraken with the command line flag:

where 10.200.0.1 and 8080 are the proxy IP and proxy port respectively. Without this flag, OAuth integrations are subject to fail.

Google Cloud Source Repositories

Due to the non-standard way Google Source Cloud Repositories use HTTPS and SSH URLs, GitKraken will have trouble parsing the URLs. The SSH URL is normally formatted in this manner:

Instead, try replacing the first @ symbol with %40:

Azure DevOps Services | Azure DevOps Server 2020 | Azure DevOps Server 2019 | TFS 2018 - TFS 2015

Gitkraken Azure Devops Server

Choose a method to securely access the code in Azure Repos, Azure DevOps Server 2019, or Team Foundation Server (TFS) Git repositories.Use these credentials with Git at a command prompt. These credentials also work with any Git client that supports HTTPS or SSH authentication.Limit the scope of access and revoke these credentials when they're no longer needed.

Important

Azure DevOps no longer supports Alternate Credentials authentication since the beginning of March 2, 2020. If you're still using Alternate Credentials, we strongly encourage you to switch to a more secure authentication method (for example, personal access tokens). Learn more.

Azure DevOps Server was formerly named Visual Studio Team Foundation Server.

Tip

Using Visual Studio? Team Explorer handles authentication with Azure Repos for you.

Note

Gitkraken Azure Devops Free

Visual Studio 2019 now includes a new Git tool that provides an improved experience when connecting to a Git repository. When you enable this tool, the Team Explorer tool is effectively disabled when connected to a Git repository. You can acquire the new tool by downloading Visual Studio 2019 version 16.6. To enable and use the new tool, see Git experience in Visual Studio (Preview).

Authentication comparison

Personal access tokens

Personal access tokens (PATs) give you access to Azure DevOps and Team Foundation Server (TFS), without using your username and password directly.These tokens have an expiration date from when they're created. You can restrict the scope of the data they can access.Use PATs to authenticate if you don't already have SSH keys set up on your system or if you need to restrict the permissions that are granted by the credential.

Use Git Credential Manager to generate tokens

The Git Credential Manager Core is an optional tool that makes it easy to create PATs when you're working with Azure Repos.Sign in to the web portal, generate a token, and then use the token as your password when you're connecting to Azure Repos.

PATs are generated on demand when you have the credential manager installed.The credential manager creates the token in Azure DevOps and saves it locally for use with the Git command line or other client.

Gitkraken Clone Azure Devops

Note

Current versions of Git for Windows include the Git credential manager as an optional feature during installation.

SSH key authentication

Key authentication with SSH works through a public and private key pair that you create on your computer.You associate the public key with your username from the web. Azure DevOps will encrypt the data sent to you with that key when you work with Git.You decrypt the data on your computer with the private key, which is never shared or sent over the network.

SSH is a great option if you've already got it set up on your system—just add a public key to Azure DevOps and clone your repos using SSH.If you don't have SSH set up on your computer, you should use PATs and HTTPS instead - it's secure and easier to set up.

Learn more about setting up SSH with Azure DevOps

Gitkraken Individual Azure Devops

OAuth

Use OAuthto generate tokens for accessing REST APIs. The Accountsand ProfilesAPIs support only OAuth.

Gitkraken Azure Devops Invalid Token Specified

• SSH authenticationto generate encryption keys when you use Linux, macOS,or Windows running Git for Windowsand can't useGit credential managersor personal access tokens for HTTPS authentication.