With Gitflow initialized in your repo, you will get an additional menu in the left panel. Start or finish any of your Gitflow branches here. Create new Gitflow branches by clicking the green button on the Gitflow menu on the left. Or whenever you add a branch, include the prefix for the Gitflow branch type i.e. Free timeline maker for communicating project milestones & deadlines.
Git is a free and open source distributed version control system designed to handle everything from small to very large projects with speed and efficiency; GitKraken: Git GUI Client for Windows Mac and Linux built on Electron. The downright luxurious Git client for Windows, Mac and Linux. Cross-platform, 100% standalone, and free. GitKraken now offers Git novices and pros a consistent experience across Mac, Windows and Linux. And makes Git operations not only performant and efficient, but understandable, visual, and perhaps even just a.
The answers to your important Frequently Asked Questions.
Just a sec! Before you dive in, perhaps one of these resources might help?
- GitKraken Cheat Sheet
- GitKraken for GitHub Users Cheat Sheet
Features & interface
Does GitKraken support TFS, Visual Studio Team Service or Azure DevOps?
Yes, for Azure DevOps (previously VSTS), you can use our integration with Azure DevOps!
For TFS instances you will need to clone your repo File Clone Repo and then enter the HTTPS repository URL (which can be found at the top-right of your Code page).
If you're connecting to a remote TFS Git server from a Mac or Linux, you will need to enable Basic Authentication in IIS for TFS.
If authenticating to TFS via username and password is not working, try creating a Personal Access Token (PAT) to use in place of a password.
For more information authenticating with repos, check out our SSH and HTTPS page.
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.
How can I see what commands GitKraken makes to the CLI?
Unlike other Git GUI clients, GitKraken is not a front-end GUI for your command line. It works directly with your repositories with no dependencies, which means a separate Git installation isn’t required.
How can I use multiple GitHub / GitLab / Bitbucket / Azure DevOps accounts with GitKraken?
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.
How do I change the avatar associated with my commits?
Your commit avatar in GitKraken is linked to the Gravatar, which is linked to your .gitconfig email address. If you change your Gravatar, your avatar in GitKraken will update itself.
Can I use my GitKraken paid license on more than one computer?
Yes, your GitKraken paid subscription is associated with your email address, not a specific computer. So you can use GitKraken on as many computers as you'd like. 🖥️
Why can't I see remotes under my integration drop-down menu?
The remote drop-down menu is for adding remotes from an integration (such as GitHub, GitLab, Bitbucket, etc.) and will only display forks of the repository. To add a remote that is not a fork, use the URL option instead.
How do I push a local project from GitKraken to GitHub, Bitbucket, GitLab, or Azure DevOps?
You need to change your branch's upstream and force push.
- Initialize a blank project on GitHub, GitLab, Bitbucket, or Azure DevOps.
- Open your local project in GitKraken.
- Add your newly initialized project as a remote using the URL option.
- Update your branch's upstream so it points to your new remote.
- Push the branch. You will be prompted to , which is the correct action to take for this use case.
You are done! Your local project is now on your hosting service.
Can I access repos for GitHub Enterprise, GitLab Self-Managed, Bitbucket Server or Azure DevOps with my Individual subscription?
Yes you can! From a new tab navigate toClone a repo Clone Clone with URL. From here enter the remote SSH or HTTPS URL and click .
How do I sign out of GitKraken?
You may sign into a different account by selecting your profile icon in the top right corner and selecting Sign into a different account.
While there is no way to sign out of GitKraken, you may delete all of your GitKraken data by deleting the ~./gitkraken folder. You can find the Data Location for your operating system here.
Technical issues
I receive a 'Could not find a compatible repository' for one of my repos. How can I fix that?
That error usually indicates something is stopping GitKraken from opening the repo. If you have this project open in another tool, such as an IDE, try closing that application and then relaunching GitKraken.
If you have CLI installed, try running git status. If you have pending changes, try stashing or committing those changes or switching branches, and see if that allows you to load the repo in GitKraken.
On Windows machines, it is possible that a file path became too long.
There could also be an issue with the directory path itself. Try cloning this repository to a different local directory.
I just downloaded GitKraken and it is not working.
If you are on Linux and are unable to launch GitKraken after installation, try to launch the application from the terminal to verify that there are no missing dependencies. Also, be sure to check out our page on How to Install GitKraken.
I just subscribed but I do not see PRO in the lower right corner.
Be sure you are logged in with the same email address registered with your GitKraken Pro subscription. Click your profile icon in the upper right corner to check which email you're using or to sign into your account.
I'm having an SSH issue.
The most common issues are:
Misconfigured SSH settings — If you are using SSH (your remote URL takes the form of
ssh://{host}/{repo}or{user}@{host}:{repo}), go to Preferences Authentication to confirm that your SSH settings are correct.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.
SSH-agent on Windows — GitKraken currently only supports Pagent for the SSH agent. You can download PuTTY and Pagent from their page here.
I can't view any of my GitHub remotes from GitKraken.
GitKraken needs to be authorized in your GitHub account in order to browse remote repositories, view and create pull requests, and perform other actions. You can double-check that GitKraken is authorized from your GitHub authorized applications page.
If GitKraken is authorized on your GitHub account, you should be able to browse and connect to any of your personal repositories. However to connect to any repositories owned by an organization, GitKraken usually also needs to be authorized by the organization. After authorizing GitKraken on your own account, you can make access requests to your organizations from here. Requests must be approved by organization owners, as explained in GitHub's documentation.
If you are attempting to use GitKraken with a repository owned by a different individual, consider forking their repository to use GitKraken for your changes. Otherwise this other individual will need to first install GitKraken and connect it to GitHub to authorize GitKraken.
I'm having an issue using GitKraken behind a firewall.
GitKraken should activate and run automatically behind standard firewall setups. Due to the highly variable nature of firewall configurations, we cannot troubleshoot individually, nor can we guarantee that your setup will be compatible with GitKraken.
I can't get GitKraken to run behind a proxy. Is there anything I can do to make it work?
GitKraken supports both authenticated and non-authenticated proxies, but some PACs and URL-based settings still may not work. If this applies to you, there are some workarounds (please note that there is no guarantee that these fixes will work for all users):
If you're having issues using GitKraken through a proxy, use the
http.proxyGit config setting. Add your proxy to this file and give it a whirl.If that doesn't work, configuring
remote.<name>.proxymight help. Bear in mind that local (repo-specific) settings override the settings your global Git config.
Learn more on our SSH, HTTPS, & Proxies page.
Gitkraken Git Hooks
GitKraken keeps spinning when opening a repo. Can I use it with repos on DropBox or OneDrive?
GitKraken does not support opening repos hosted on DropBox or OneDrive. We recommend moving your repo to a location on your machine, and then opening the repo from there.
My commit graph is not showing up correctly.
Sometimes a repository can get in an unexpected state that causes it to not work correctly in GitKraken. This may be your commit graph not showing up at all or seeing the message 'Displaying 2000 commits'.
Try running git gc from the terminal on this repository and then relaunching GitKraken. You can also try taking a fresh clone of the repository in a new location.
My files are not showing up as expected or are marked as binary.
GitKraken Git GUI only supports UTF-8 file encoding. Files may display in an unexpected way or be marked a binary if files are not encoded in UTF-8.
You can use and external diff and merge tools to work on files using other encoding types.
Can't find your question here? Contact us and ask away.
Whether you are a newborn or a wizened deep-ocean octopod, this Getting Started Guide uses a basic workflow to provide an overview of the GitKraken interface from cloning your repository to successfully executing Git actions.
Learning Git with GitKraken
In this series, we'll provide Git tutorial videos. You'll learn Git concepts and how to apply them in GitKraken.
Interested in how version control fits into a DevOps workflow? Check out our DevOps Tools Report to learn more.
GitKraken Tutorials
Need a hand jumping into the product? Here's a playlist with a few video tutorials.
Define local
Most of the work you do in GitKraken is using the local repository, meaning the files and changes are saved on your local machine.
You can easily identify any local branches in the graph as they are shown with the icon.
One of the reasons why Git is so fast when compared to other SCM tools is because all changes are made locally rather than on a remote server. The local repository includes all of the branches, and changes made to the repo, since the time it was created.
Because you make a copy of the entire remote repo, you can change branches, view history, and commit changes without needing a network connection. It also means if there is a catastrophic event on the remote server, or if another user makes an unwanted change on a remote, all of the other members of the team would still have a copy of the full repo so it can easily be restored.
.git folder
When initializing a Git repo or cloning from a remote, you will notice a .git folder in the project root. This contains all of the information required for the Git repository and if this folder is deleted, you would no longer be able to switch branches, pull from remotes, or view commit history.
Working directory
The working directory is the currently checked out version of the files in the local repository. When you change branches, pull in changes, or reset, GitKraken will update the files in the working directory to reflect the changes.
For more information on Git repositories, check out the Git repository tutorial blog post including a video from one of our developers.
Workflow Example
Once your repository is initialized and the interface is out of the way, it's time to get cracking ... Whaahh-pssh! ... and tie all of the interface and concepts together to perform work on your repository.
Up until this point, you have created an entire folder representing your project with great potential. With this example, we'll take the next step and make a commit to production in a basic workflow.
Branching
The newly initialized repository created results in a default master branch. Synonymous with production, typically commits are not made directly to this, but rather are reviewed and merged in.
Branches can be thought of as an area to silo where to commit. Its reference is specifically a moving pointer to an individual commit object.
On our newly created repo, we'll branch off from master to silo our normal development. To do this, right-click master on the graph and select Create branch here. Let's call this branch develop in 'enter branch name' which is going to be an indefinite main track branch to the project.
Gitkraken Git Flow
Once created, GitKraken will auto checkout develop and switch to that new branch.
Changing file content
Now that develop is set, we can make some new changes without affecting anything on production.
In the example, the README.md file was created automatically to provide context about the project. This involves creating the file, writing content, and then saving it to disk. With Git, the last step to save becomes more granular in order to write desired changes for revision history.
README.md was created as a placeholder and the project can become more meaningful by modifying the file with the project context, as well as adding additional project files. Any modifications and additions will have to be staged and committed, which will only affect our current branch.
You can select Initial Commit from the graph, and click README.md to open the built-in editor.
Staging and Committing
Say you made changes to the README.md file. When selecting the //WIP node, there will now be pending changes to README.md in the staging panel under Unstaged Files.
Next, let's move these changes into the Staged Files section by selecting the green button.
Outside of Git, work is done in a typical File Save method or written automatically when changes are detected. In a way, committing in Git is like the Save, where we've made a pointer to the changes in this current version of the file to keep in history.
From here, type a brief summary of your changes and click to save your changes to the README.md file. This effectively updates the reference on develop, pointing to your first modification after Initial Commit.
It's easy to distinguish between different types of changes including Added, Modified, Renamed, and Deleted files.
Visit staging for vast coverage of the topic, including staging individual lines or hunks of file changes. Be sure to check out commits too.
Merging
Now that our develop branch is up to date, we want to roll out these changes into production.
From the graph we see that develop is ahead of master by exactly 1 commit.
In order to add this commit into the original branch, we will merge develop back into master. This will take all of the changes introduced since the last commit and play them on this branch by performing a new commit (called a merge commit) with the changes.
There are a few ways to perform the merge action in GitKraken, but perhaps the easiest is from within the graph.
In the graph, you can see we have things in a new branch, develop, that we want in our source branch, master. Like any sensible person, we would only have to pick up develop and throw it at master right? Right! Simply drag develop and drop it on master to get the merge option.
Gitkraken Git Gui Individual
Alternatively the same merge can be performed through right click and other means. Revisit and learn more about merging and other options available through Branching and Merging.
Summary
In the end, this is as simple as it gets in terms of workflow and paves the way for incorporating changes into pushing and pulling or venturing to advanced models like GitFlow.
Remember, you must crawl before you can walk and without a doubt you will be running in no time!
Below is a sample video on how a simple commit is created as was explained in this guide. For more topics checkout the rest of the categories and pages listed.
Git Gitkraken Guide
Your quest continues!