Git GUI vs Command Line
Tags: git
Published: 2021-04-07 13:19:34

---
published: true
description: "GIT GUI Vs Command Line"
tags: [git]
title: Git GUI vs Command Line
cover_image: https://res.craft.do/user/full/e08d0ba1-ee73-de35-2f90-2e261c097071/doc/82149C1E-E8FF-4BBE-8EA8-FE551C5A7E68/F0D084C3-63A4-4A06-80C7-CD0D918FDBD0_2
canonical_url: https://cctplus.xyz/2021/04/07/git_guivscli
---

# Git GUI vs Command Line

{% youtube fpO_Qt8_h7s%}

In the past couple of posts, I’ve been using the command line to interact with Git, but you don’t have to do that! You can actually use an application to do git commands. If you haven’t guessed it by now, today, we are going to talk about using an app for git versus using the command line.

# Now, you might be wondering, **why** would you want to use an app to interface with Git instead of the command line?

Well here are some reasons:

- Graph view of commits
- Graph view of branches
- See the changes and explore them more

![Fork](https://res.craft.do/user/full/e08d0ba1-ee73-de35-2f90-2e261c097071/doc/82149C1E-E8FF-4BBE-8EA8-FE551C5A7E68/E89B5766-746A-4DA2-B008-3A660116D2D6_2)

It’s really nice to be able to see all of this in a more user-friendly way. Yes, you can see this all through the command line, but it can be a bit easier to read in an app also might be a bit easier to use. Especially because you don’t have to remember the commands.

Most Apps will also let you set up your remote server account like GitHub or GitLab so that you can clone from the app which also avoids the command line.

There are so many options when it comes to using an application for Git. The three that I’ve used are

- Fork
- GitKraken
- Tower

They all work on Windows or Mac and can be used together if you want. Each app offers something a little bit different, so I highly suggest you try them out and see which one you like best. I like Fork the best since it can handle private repositories for free. To support development, the developers do charge around $50, but you can bypass that if you want.

# Now, how does the app workflow compare to the command line?

Well, the workflow is the same. You still add your files, commit the changes with a message, and push them to the remote server. There are just some buttons to hit instead of typing the commands. Let’s look at how Fork does it since that’s what I use as my client.

First, we need to go to the repo.

Then to add files, Fork actually has us check them to acknowledge the change and then stage them.

Now, we add our message and hit commit!

That’s pretty easy to do on the command line even, but where I think Git Clients/Apps/GUIs whatever you wanna call them really shine is when you need to do something a bit more complex like switching branches and adding tags, which I use a lot in my workflow.

If you need a reminder on how to switch and create branches via the command line, check out this [post](https://cctplus.xyz/2021/03/17/giting-tree) about branching strategies.

Here’s how I’ll create a branch in Fork. It’s relatively similar to all the other apps.

1. Right-click on the current branch
2. Choose create branch
3. Give a branch a name
4. Click create

Now, isn’t that pretty easy?

These are some of the niceties that come from an app.

# Which should you choose?

Well, that’s not really a question I can answer for you, but I can say I still use the command line regularly even if I have an app installed. It’s a “what tool will do the right job” type answer. If you have a preference, then let me know in the comments below!

If you got something out of this post, make sure to let me know in the comments below!