I HIGHLY RECOMMEND FOLLOWING MY GUIDE, ‘Getting Started with Git CLI for windows (Git Bash)‘ BEFORE YOU START READING THIS PAGE!!!
- What is Git?
- What are ‘branches’?
- Getting Started
GitKraken is a GUI Client for Git . What that means is that it’s software that gives you a graphical view of what is otherwise being written line-for-line in GitBash. Tortoise is also a GUI Client, though Kraken and Tortoise operate very differently. While Tortoise attaches itself to your right-click menu in Windows, Kraken is a fully-fledged, standalone unit of software that attempts to manage all of your git commands in a single interface.
GitKraken has quickly become my weapon of choice when working with Git . I still resort to using GitBash in the event that something goes wrong… once or twice, the push or pull buttons have become unresponsive for some reason… anyway, it’s pretty, it’s cool, it’s easy to use, and easy to get started!
As usual, we need to install our client (GitKraken). The installer can be found at https://www.gitkraken.com/. Download the installer and run it. You can simply spam the Next button. All the defaults are fine during the installation.
THEN, as usual, we need to provide an SSH key so that our client (GitKraken) can speak to our sever (GitLab). If you’ve followed my guide, Getting Started with Git CLI for windows (Git Bash), then you already have an SSH Key, and can simply follow this easy step (otherwise, skip to the next heading):
Of course, the path you see will have YOUR username in it, not Regan (MY username). Anyway…. that’s done.
What if I didn’t have SSH setup from the terminal before-hand?
I still think a couple lines of code in GitBash is nothing to complain about when setting up SSH, compared to Tortoise anyway. But GitKraken gives the terminal a run for it’s money here.
- Browse to File > Preferences > Authentication, hit the Generate button, and when it asks you where you’d like to store it, just choose somewhere that makes sense to you, I would choose my dev folder, as this holds all of my Git projects:
At the time of writing, there’s a bug which prevents the key from updating after it’s generated, simply browse away from the Authentication menu and then back to it, and it will have updated with your new key.
Lastly, hit the copy-to-clipboard button to the right of the ‘SSH Public Key field’ and that’s all you need to do in GitKraken.
- You have your SSH Key copied, now you just need to paste it in to GitLab as demonstrated below:
That’s it. This is the slightly more complicated route, but still easy enough, and easier than Tortoise.
Now that you’ve got your Kraken all nicely set-up, you probably want to know about Working with GitKraken for Windows.