GitKraken or How I Learned to Love Git

I’ll be honest. I don’t have a lot of experience in git.

Most of my experience, for one reason or another is with SVN and TFS.

At my day job, we made the decision to move from TFS to Git (specifically GitHub) and the transition hasn’t been easy….to say the least.

We also decided to utilize branching when we moved to GitHub, which we never did in TFS. I’m not sure why we never used branching with TFS…it wasn’t my choice or decision to make.

I realize that a lot of git gurus are command line all the way but I’m an extremely visual person. In order for me to complete my absorption of knowledge, it helps tremendously to see a visual representation of something. This can take many forms, PowerPoint presentations, flowcharts, diagrams, etc.

Enter GitKraken.

As a beginner GitHub user, GitKraken has been invaluable in understanding Gitflow (which we decided to implement for all the devs). Setting it up per repo is really easy:

GitKraken does an awesome job of showing you visually, what’s going on with your repo:

gitkraken screenshot of repo

You can see in the screenshot above, that I’m working with two branches currently, main and develop. This is a solo project so Gitflow is kind of overkill in this instance. I always have develop checked out and work from that locally. When I’m done and do a commit, I commit to origin/develop and then submit a PR to origin/main from origin/develop. This is a flow that works well for me when I’m working on solo projects.

As of version 7.6.0 of GitKraken, I can also merge my PRs right inside of the client too.

GitKraken has made the move from TFS to GitHub much smoother for me and my team and I cannot imagine doing anymore software development moving forward, without it.

I plan on posting a lot more of my love for GitKraken soon…