GitKraken can connect to repositories hosted on most services (like TFS, AWS CodeCommit, Google Cloud Source Repositories, custom service, etc), over HTTPS or SSH.
Enjoy the videos and music you love, upload original content, and share it all with friends, family, and the world on YouTube. Learn how to add and remove files in GitKraken. Add a file to GitKraken using the Fuzzy Finder. To initiate the Fuzzy Finder, hit Ctrl/Cmd + P, type Create File, and hit Enter. You can also right click the empty space in the commit panel and click the Create File context menu option. Type the desired filename and hit Enter. Removing a file. You actually won’t be using the git branch command to delete a remote branch. Instead, you will be using the git push command. Next, you will need to tell Git which remote repository you want to work with, followed by the -delete flag, followed by the branch name. It should look something like this. We’ve found that GitKraken is a good visual tool for artists and designers that need to interact with Git repositories. GitKraken is free so long as you are not using it on private repos. If you use it on private repos, it’s $29 per year. GitKraken is also bundled with a very good alternative to Trello that is much cheaper.
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:
Pushing and pulling are the keys to collaboration. 🤝
Adding Remotes
To add a new remote, click the icon when hovering over Remote in the left panel, then fill in the remote URL.
When using an integration such like with GitHub or Bitbucket, select the remotes from your collaborators in the dropdown box. This makes viewing other forks of the same repository quick and easy.
Note: When using an integration, the drop-down box will only display Forks of this repository. If you would like to add a remote that is not a fork you can still do so via the URL option.
Gitkraken Remove Repos
You can identify remote branches in the graph through the following icons:
- — GitHub
- — Bitbucket
- — GitLab
- — Azure DevOps
- — Other Remote Server
All remote branches are located in the left panel.
Push
Pushing takes any local changes , and making them available on the remote .
Push the currently checked out branch by clicking Push in the main toolbar, or by right clicking on the branch, and selecting Push.
Pushing attempts to upload any new commits to the remote branch, then fast-forward the remote to bring it up to date with the local repo.
If the remote branch cannot be fast-forwarded, the push will be refused. If this is the case, GitKraken will provide the option to Pull (fast-forward if possible), or .
Caution: Forcing a push is considered destructive because it overwrites the remote branch by replacing it with the local branch.
If the branch pushed does not exist on the remote, GitKraken will prompt you to name and create the new remote branch. This is typically the fork name followed by a slash, and the branch name. i.e. origin/my-branch.
Drag and drop to push
Drag and drop a branch to a remote to access the Push action. You may drag a branch to a remote branch on the graph, or to a remote branch listed in the left panel.
Fetching
Pulling and fetching take updates from the remote and get them into our local repo.
Fetch All
Fetching gets updates from remote branches, but does not update any files in your working directory.
Updates will appear in the graph, and also update any branches on the left to show how many commits you are ahead or behind.
When you're behind the remote, it means that there are commits on the remote branch which have not been incorporated into the local repo. Pull (fast-forward if possible) to get these changes on local.
If you are ahead of the remote branch, there are local commits that have not yet been pushed to the remote.
It is possible to be both ahead of and behind a remote. However if you are both ahead and behind a remote, you will not be able to perform a Pull (fast-forward if possible) as the branches have diverged. Consider rebasing onto the remote first.
GitKraken automatically fetches updates from your remote repositories every minute by default. You can change this setting from Preferences General menu.
Fast-forwarding
Fast forwarding moves the currently checked out commit to one that was added later, replaying all commits in between in the order which they happened.
To fast-forward your currently checked out commit, you can right click on the branch with newer commits, and select the Fast-Forward option from the menu.
Pulling
Pulling first performs a fetch and then incorporates any commits in the remote repository into the local copy.
There are three pulling options. Let's demonstrate what each one does by starting with an example 2 commits made locally, and 2 that have been made on the remote.
Pull (fast-forward if possible)
Pull (fast-forward if possible) fetches any updates on the remote branch, then attempts to fast-forward the local branch. If a fast-forward is not possible, a merge will be performed.
This is the default option for new GitKraken users.
Pull (fast-forward only)
Pull (fast-forward only) fetches any updates and then attempts a fast-forward. If a fast-forward is not possible, GitKraken will not make any changes to the local repo.
In our 2-commit example, a fast-forward is not possible as there are new commits added to both branches.
Gitkraken Remove Report
Pull (rebase)
Pull (rebase) stashes all commits on this branch, pulls in new commits from the remote, and then replays your commits. This has the added benefit of maintaining all commits in a single line, as opposed to creating branches which are then merged back together.
Note: Remember the golden rule of rebasing, 'Never rebase while you're on a public branch', which is covered in our blog post.
Setting a default pull option
Set the default pull option by clicking the down arrow to the right, and clicking on the circle button by each option.
Our interface page covers this and more.
Setting the upstream branch
Gitkraken Remove Repossession
Whenever pushing, pulling, or fetching, GitKraken gets updates from the Upstream branch.
The Upstream defaults to the remote branch where the local branch was checked out, but you may change the Upstream to push, pull, or fetch from different branch.
Right click on a branch to set the upstream or click the option.
Alternatively, drag and drop a branch to push instead of setting upstream.