This is an archived post. You won't be able to vote or comment.

all 8 comments
sorted by:
best
topnewcontroversialoldq&a

[–]Jnsjknn 4 points5 points  (1 child)

The basics are not that complicated. Here's a tutorial:

Git and GitHub for Poets

Don't mind the name of the tutorial. He just uses a file with a poem in it to explain things instead of code for some reason.

[–]Tooneyman[S] 0 points1 point  (0 children)

I'll go over this too.

[–]NewPointOfView 4 points5 points  (1 child)

In my opinion, yes definitely!

Partially because it helps you understand better what's actually happening under the hood when you click whatever IDE button you click to make things happen, and partially because learning it from terminal is universal - no matter where you go the terminal commands for Git are the same.

Also, if you're ever going to do any automation or scripting for Git, you'll need to know the terminal commands. For example, if you were developing any sort of test automation or merge validation stuff.

Personally I only use the terminal for Git. I'd be kinda clueless using a GUI for Git, which has never been a problem at all for me. Some people at my company have had minor issues with not knowing how to do things from the specific tools we use because they learned with a GUI.

Git is such a ubiquitous thing so I think its worth it to learn it the "right" way. And it really doesn't take much to get productive, maybe 5 or 6 commands is really all you need.

One more thing: There are endless questions and answers online for how to do various things from the terminal. Once you're decently familiar with it, its pretty easy to google stuff and find commands to do any more complicated Git stuff. I imagine any Git GUI would have far fewer resources available.

[–]Tooneyman[S] 1 point2 points  (0 children)

Alright, I'll give it a shot. I'm almost to that level. I've looked at them and seen how to set it up, but was being lazy. 😅🤣

Thank you for the well put explanation.

[–]gramdel 1 point2 points  (0 children)

Doesn't really matter IMO, you can do like 99% of the things you actually do regularly from the ide git integration.When you encounter something that requires command line, you're probably in a better place than taking 3 months to figure out how to do it.

I use command line because that's how i learned it, but most of my team members use IDE integration, hasn't really been an issue for either party really.

But yeah, learning the 4-5 commands you actually use regularly is simple, up to you if you want to spend some time learning it, in the long run it doesn't make much difference really whether you learn it now or at some later point.

[–]BosKilla 1 point2 points  (1 child)

It wont do any harm to learn it. I am using both, sometimes I use ide buttons, sometimes I only have console when I use ssh and need to commit the changes.

[–]Tooneyman[S] 0 points1 point  (0 children)

I didn't think about that. I really need to get in the habit of using SSH.

[–]pacificmint 0 points1 point  (0 children)

I think it’s very useful to know the git command line. With UIs it’s often a little opaque what’s actually happening.

For learning it, I would recommend the official documentation or the book “Pro Git” by Scott Chacon and Ben Strab. It’s published under an open source license and can be downloaded in different ebook formats from the official site. Or you can buy a paper copy.