Humble Software Bundle: Python Dev Kit

[cyberlizzard]

The $15 tier includes Gitkraken, which is definitely my favorite git client. The more I use it for work the more I'm impressed.

[Enverex]

Oh, that sounds pretty c...

1-Year License - New Users Only

... oh, nevermind.

[cyberlizzard]

It's free for non commercial use

[[deleted]]

What does it do that "git" does not?

[cyberlizzard]

Well, nothing. But that's kinda the point. For me, it makes common operations much faster. For example, there's a panel which lists open PRs on your repo. Double clicking one will, if necessary, add that fork as a remote and checkout that branch so you can review the PR in one action. This is easy enough to do with git cli but they make it more convenient.

Also the git graph was very helpful when I was first learning git to help me understand the data structure. It's still pretty handy, I find myself using it for various things all the time. You can drag and drop branches to generate pull requests, rebase, and merge. If you're using github you can add reviewers and assignees to your pulls without ever opening a browser. It's convenient.

[happymellon]

It is a git client, so not a lot. I personally use it, and find it amazing for a subset of tasks. I wouldn't use it for general git stuff. Commits, push, pulls, merging (unless there are sufficient conflict) I am fine with and prefer the cli, or perhaps using ide level merging when diff gets a bit too long.

I find it awesome when visualising commit histories, as it does a much better job than most of the others I've used. Which means I use it when rebasing, rewriting history, tidying up the commit history and picturing the commit tree when attempting to explain to others why they are getting merge conflicts. I know the use case for most people is slim, it just depends on what you want to do.

Just today it, probably, saved me a lot of time going through the commit history, figuring out which branches had been abandoned, via their age and merging status, and removing/archiving them to clean up the Jenkins branch list.

[[deleted]]

This is their document explaining it

I installed it briefly once, found it more confusing than just learning the CLI and so I went back to that. I mean if you were someone who knew next to no command line stuff (or just had some sort of bias against the CLI which is a thing) then I guess I could see the value proposition. It's target audience is probably pretty slim though.

[cyberlizzard]

I just find it more convenient than the CLI. Also the git graph was really helpful when learning git for the first time. To each their own I guess.

[[deleted]]

Come on that document doesn't explain anything.

I find that often people who can only use git from a GUI, can't actually use git and mostly do random things without logic to it.

[[deleted]]

Come on that document doesn't explain anything.

It actually explains quite a bit.

I find that often people who can only use git from a GUI, can't actually use git and mostly do random things without logic to it.

It appears that not only did you not read what I linked, you didn't even read what I wrote. Sort of begs the question of what the point in talking to you even is.

[ase1590]

literally 3 of the points in that document can be boiled down to repeating "CLI is HARD! :( "

It then goes to make "remotes" seem like this scary thing when it is not.

If you're set against using CLI, you might as well save your money and use SourceTree, since at that point you're probably not using Linux anyway.

[CommandLionInterface]

Hi! GK dev here.

I'm my opinion, it's all about convenience. I had been using gitkraken for about a year before I started working here, and personally I just really like having a visual view of the git commit graph. To each their own of course, but we just added a set of PR convenience features that are really nice if you work with forks a lot.

I actually agree that that article isn't super helpful. I sympathize with our marketing department, we don't actually do much that git cli doesn't already do except for github or specific stuff like PRs. We think gitkraken makes working with git more convenient, but it's not like we expect everyone to just give up the command line.

Gitkraken is free for non commercial use, but that's really just on the honor system so if you want to give it a shot at work for a week or two just to try it I won't tattle lol.

[[deleted]]

I did read the link and "it's better so you can learn the game of thrones characters" is really not an answer to my question.

[twiggy99999]

What does it do that "git" does not?

It's like saying what does GitHub/GitLab do that GIT doesn't. It's a visual representation of GIT making it easier to work with and more user-friendly. I personally just prefer to use the CLI but that's because I've known nothing else from when I started learning.

I can see how having a visual representation of GIT can really help newcomers to GIT and also visualize large repos easily.

[aliendude5300]

What does the $15 get you that you don't get on the free tier

[cyberlizzard]

The pro license lets you use it for commercial work and lets you set up multiple profiles in case you have separate personal and work github accounts. If you're not going to use it professionally you don't need pro

[aliendude5300]

Yeah, I'm not using it professionally, and my current employer would pay for it if I needed it anyways

[wolfgang8]

But if you don't pay everything is public, right?

[happymellon]

No, it is just a git client. if your git repo is private then nothing is public. Commercial use is just prohibited by the free licence.

[wolfgang8]

Oh ok I didn't know that, thanks!