How to be a git expert

Learn git concepts, level up your command line skills, and become a more capable git user!

[krzysztofkaminski]

Great git walkthrough. No fluff, good pace and clear explanations with visuals.

[cusematt]

This is the most helpful git tutorial I've watched, thank you for breaking it down into the basics so clearly.

[davirafacho]

what an impressive tutorial, I've been looking for content like this for months

[jan]

Thank you very much. I have seen many many GIT tutorials but this is I think one of the best! I will recommend it to my students (still) struggling with GIT!

[TheMassgames]

Great presentation! Very clear and concise with some nice graphs. Thank you for this!

[shoooozzzz]

Proud member of team rebase and I like the clean git history. Once you understand rebasing, it's not so scary.

[jmSD]

This was the plain english git sanity check ive been looking for for a long time, thanks. Just subscribed.

[MrKaizen]

Very helpful tutorial! Thanks a lot for making this!

[igorsantanas]

That was a great tutorial. Thank you for sharing your knowledge!

[nouman]

The information in this video is like... NON-STOP! Constant knowledge. Had to pause it multiple times to just let it sink in.
LOVE IT!!! Thank you

[gurditrehal]

If you don't want to stage an entire hunk with 'git add -p' and just want to stage a few lines, you can use 'git add -e' to pick and choose which lines you want to stage without using a separate tool like git-cola.

Also, if you want to write a commit message with a body, you can use 'git commit -e' to type in a title in the first line followed by an empty line then write your commit message body on the third line.

[sfalpha]

This is good one on the all concept of Git.

But things I want to add is about cherry-pick. General use case for cherry-pick is to maintain the old version or the release version of the software/branch.

Let's say you maintaining version 1.0.3 for old system while current release is now 2.x. So it not ever gonna get merge. So you have bugfix in 2.x and you want to use that commit on 1.x also, that when you actually do the Cherry-pick and tag it as 1.0.4.

Another case is maintain the production release. I also use cherry-pick a lot to apply hotfix to the production release and then when the testing on new release is done we can do merge again. And usually with cherry-pick I do alter some commit messages to say that this is hotfix. so when the actual fix may get merge later log history will not look too obvious.

[scottfranco]

One hint for any git user: if you are doing something complex with git say to repo a (which is a full directory), doing "cp -r a b", ie., making a full copy of the entire repo, can really save you. Git does nothing until you commit and push. You can always go back to the previous copy of the repo and start again. Further, if you get used to working on the tree level, even with big trees, life can be good. For example "diff -r a b" (compare two entire directory trees), or better yet "meld a b" give you complete comparisions of repos. Finally, learn to manipulate patch files. Git is based on patch files, and they have existed longer than git. Git is basically an automated patch file program. Learning how patch files work is like learning the assembly language of git.

[peternavarrete]

just started watching but this is exactly the type of video I was looking for. thanks!

[satishmeghavvarnam]

The content and presentation is great.

For those that are long time unix / Linux users, ' man git <cmd> ' is another way to look up help for any git command

[weatherwaxusefullhints]

The best thing i have seen about git! Thank you so much! Now i can wear my git-fan shirt without feeling like a fraud 😊

[radosawszostak]

The best git tutorial I've seen so far, thank you. EDIT: sound volume little to low, imo

[naco]

Fantastic video, exactly what I needed.

[brandondenis]

Wanted to say, I use "git add -i". Interactive mode is super useful to show which files have been modified, and then to select if you want to patch them, individually or add untracked files all in a fairly easy to use interface.

[saliexplore]

this was awesome, thanks for sharing :)