Welcome to the Treehouse Community
Want to collaborate on code errors? Have bugs you need feedback on? Looking for an extra set of eyes on your latest project? Get support with fellow developers, designers, and programmers of all backgrounds and skill levels here with the Treehouse Community!
Looking to learn something new?
Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and join thousands of Treehouse students and alumni in the community today.Start your free trial
Using the command line to use Git vs the Git app
I've only just started learning about Git, and the command line is daunting. However, I've come across a Git app, which you can use to accomplish the same tasks, but with a GUI. Is there a reason that you should use the command line over this app?
There are pros and cons for both methods of interacting with Git. I think starting with the GUI is great so that you can learn how to do various tasks like branching, writing commits, pushing, pulling, etc. The problem with only using the GUI is that it abstracts a lot of what is going on. There are times when you might want to do things like rebase, or if you have multiple merge conflicts, where knowing how to use the command line makes it a lot easier.
For the most part I've been able to get away with only using the GUI, but in the past year as I have started doing more serious open source contributing, and working with larger teams, having a deeper knowledge of the command line has come in handy for some very specific circumstances (working in multiple environments where I only have terminal access for example).
If the GUI gets you using Git, and it covers all of your needs for now, that is all that matters.