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:
GitKraken is a tool designed to manage GitHub repositories via a GUI interface. You can open, clone and create completely new repositories. To start working, you have to log in to GitHub or Bitbucket. However, you can avoid entering login details thanks to your SSH key. SmartGit is a Git GUI client with support for GitHub, BitBucket, GitLab pull requests and comments. SmartGit targets professional users.
- GitKraken: Git GUI for Windows, Mac & Linux Visual Studio Codeと同じくElectron製のアプリです．UIも直感的でなんとなくで使っていけるかと思います． コミットのツリーから各コミットの変更ファイル，そしてそれぞれのファイルの変更内容がスムーズに確認できます．.
- When viewing the diff of tracked LFS files in GitKraken, you will see a versioned URL, a generated SHA, and a size pertaining to the size of the original contents of the file: Git LFS stores the binary file content on a custom server or via GitHub, GitLab, or BitBucket's built-in LFS storage.
- What Linux distributions are supported by GitKraken? GitKraken currently supports Ubuntu 16.04 LTS+, RHEL 7+, CentOS 7+, and Fedora 30+. While GitKraken might be able to be installed on other distros, we cannot guarantee that it will behave properly.
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
Gitkraken Linux 32 Bit
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.
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:
Git Rebase in the Command Line
To begin your Git rebase in the terminal, you will likely start by running the git branch command to see a list of your local branches. In the example below, you can see the currently checked out branch is feature, along with two other branches: dev and production.
gt;In this example, let's say you want to rewrite the two most recent commits from the feature branch onto the dev branch. Because the terminal lacks the immediate visual context of which commits exist on which branch, you will start by running the git log command followed by -2.
The commit named Additional sentence structure changes is where the feature branch originally branched off from the dev branch. This will change after the Git rebase is completed, so take note.
From here, you can hit q to exit the log.
To proceed with the rebase, you will use the git rebase command followed by the name of your target branch—in this case, the dev branch—to move your changes from one branch to another.
With that, the rebase is complete! Git has re-written the commits from your feature branch onto the most recent commit on the dev branch.
Because you're unable to immediately verify the success of the rebase in the CLI, as you can with GitKraken, you should double-check by running git log -2 again. And voila! We now have a new base commit on the feature branch: Finalize release date.
GitTip: feeling like you've got the hang of rebase? Graduate onto Git interactive rebase.
Stop wasting time on commands and get more time back in your day to….do whatever you want. Download the cross-platform GitKraken Git client free today.
Gitkraken Linux Alternative
Still not convinced? We've a two-part tutorial special comparing rebasing in GitKraken with rebasing in the command line. Spoiler alert: in part 2, you'll even see what happens when a conflict occurs.
