#Gitkraken open source for free#
#Gitkraken open source how to#
#Gitkraken open source install#

I assumed a mistake had occurred - true, I didn’t have a Pro account, but nor was I using a Free account. If you require additional assistance please upgrade to GitKraken Pro.

#Gitkraken open source install#

If you have installed the GUI via snap please try one of the alternative install options detailed here. Our team does not test again this distro and we cannot guarantee that the GitKraken Git GUI will behave properly. Additionally, it’s important to note that the GitKraken Git GUI does not support Pop!_OS. For guaranteed support please upgrade to GitKraken Pro.

#Gitkraken open source for free#

We currently do not provide support for free accounts. Thank you for taking the time to reach out to support. In Preferences -> General, both the External Editor and Default Terminal dropdowns have as the only option. I’m using GitKraken 7.0 on Pop!_os 20.04. I saw a menu item in GitKraken, though, that said, “Send Us Feedback,” so I sent the following:

#Gitkraken open source how to#

I poked around a little bit in the UI, ran a few google searches, and came up empty on how to resolve this. When I tried to select a different editor, I saw that my only option was “”: GitKraken Preferences I found the Preferences screens, and saw I could configure an External Editor and a Default Terminal. And I continued to use GitKraken.Īfter some days or weeks of use, I decided to really dig into GitKraken’s settings and understand its suite of offerings. Since I have no enterprise needs, but I do want to work with private repositories, I paid $29 for an Individual license. Pro adds enterprise features: user management, GitHub Enterprise, etc. Among other things, Individual lets you access private repositories.

Pro (“For teams and companies” - $49/year).

Individual (“For individual developers” - $29/year).

After a few days using it, I decided to show my support by purchasing a license (preemptive snark: “People who use Linux don’t pay for software!”). It ticked all the boxes for me: intuitive, beautiful, and feature-rich. I installed GitKraken and began using it. Back then, though, I’d already cast my lot (and my money) with Tower, so I never dug into GitKraken. I’d tried GitKraken on macOS years ago, and thought it had promise. I asked Slant what Linux Git GUI was best, sifted through some editor plugins and “minimal” clients, and decided to try GitKraken. What they don’t have, however, is a Linux version (preemptive snark: “That’s because people who use Linux don’t use GUIs!”). I have this hanging by my desk at the office I haven’t seen since mid-March. Updates come frequently, and they even have cool merch. It’s beautiful, intuitive, feature-rich, and powerful. I mean, I can google “cherry pick” for those rare times I use it, or I can choose it from the menu and not worry about mangling things in Git history. Why? Primarily for reviewing diffs and history, or for performing rarely used operations. The CLI is usually quicker, and I’m usually in the terminal anyway, but yet I also use a GUI.

Not always, and not even most of the time.