7 Git Tips To Overcome Your Fear of Version Control

Working with a team of skilled devs and afraid you'll screw the codebase up?

Worried you're going to overwrite other developers' commits? Or get a complex merge conflict that you can't resolve?

Well, this video is for you.

In this video, I'll offer 7 Git tips to help you feel more confident with Git, GitHub, and Version Control in general.

Timestamps
00:00 - Intro
01:30 - Tip 1
03:15 - Tip 2
05:55 - Tip 3
06:18 - Tip 4
08:34 - Tip 5
10:14 - Tip 6
10:48 - Tip 7

Recommended Git Course

** Career Path Coding Tracks **

** My Coding Blueprints **

** I write regularly **

** FREE EBOOKS **

LET'S CONNECT!

#git #github #versioncontrol #coding

** Some of the links in this description may be affiliate links that I may get a little cut of. Thank you.

[leoMC]

At first I hated Git, I tried to use it and lost an entire day of work. But after learning the basics and work on my own projects I did the opposite: saved my project thanks to Git. Still, I'm scared of working on it on a big corporate project. It's like you read part of my mind with this video. Thank you so much. 👏👏👏

[manojkumar-jtfw]

Inspired by Travis journey and started learning DevOps. I completed
1.Liux Administration (20hrs)
2.Bash Scripting (17hrs)
Right now learning Git (22hrs)
Next will b AWS. (Will prepare at the level of Solutions Associate Architect)

[aashish_aryal]

Your channel is a gold mine. You have helped and motivated me to learn. Thank you ❤

[ahmedb.hameed]

Thank you for this video. Always appreciate such videos where people sharing knowledge. In a large team, tracking commits that comes from merging is not a trivial thing. The history shows like circuit diagram. While rebasing might be hard as you have to go throw every conflict in those commits and resolve them, but the outcome is a clean git history as rebasing will create new commits hashes.

[SchnippSchnappShnappi]

This has helped me a lot. Git used to be my personal horror I even wanted to quit my studies just for this reason many times

[kenhaley]

Coming from other VCS systems, I have to admit that I found GIT a bit frustrating to learn. Git has more commands, and they work differently. I suppose it's partly because GIT maintains a local repository on the local machine so you can work off-line--including pull, commit, etc. So, I think my learning curve was more about making sure I understand the terminology...that is, exactly what commands do what. This is a great video to help understand that. And I love explanations that say WHEN or WHY you would use the different commands--something that's not always clear in the docs. Also, the tip about using VS Code to do ALL git functions is great. I suspected that was true, but I wasn't sure.

Thanks for making this video!

[korg]

These tips are awesome, would have been helpful when I started my job earlier this year that first dipped my toes into DevOps but it's still helpful to me now!

[ventin]

Thanks for the tips Tavis. Those encouraged me to keep exploring.

[samarbid]

Here is another one:
You forked an opensource proj, after your change is been accepted and merged, your forked repo is still saying that "you are N commits ahead, "
to sync it with the upstream you can run:

git checkout master
git reset --hard upstream/master
git push --force

[reloadfast]

CLI vs UI has been a rivalry since graphical user interfaces exist... there is no right or wrong, no work flow optimized way of doing, there is your preferred way and that's it. Do it however it comes natural to you.

[mikeschinkel-newclarity]

"Don't work about Git rebase, especially if you are working on a large project with lots of developers."

Great advice, unless those in control of that large project dictate that everyone shall always use `rebase`, never `merge`. 😉

That was the case for my last major client. #fwiw

[salahiddinediouri]

this really interested use Cases, thank you for sharing

[dimitriskarathanasis]

Thank you for sharing! That was a great video!

[irfanghat]

Everywhere I go, I see version control. I'm fine with everuthing else but, that thing scares me especially when you involve pipelines for continuous integration and development.Every second feels like I might screw up. Thanks for the video.

[maou_raizen]

please please please make a detailed video of merge conflict

[kalideb-yy]

on tip 1: What if after you just did the "git pull" to fetch new changes from remote repo then after just a few seconds some devs pushed commits to that repo? so your local repo will not up to date again 🤔🤔🤔😅

[LearnQtGuide]

Is that copilot completing your commands on the terminal? That's pretty neat!

[Quintusflac]

Any one use Tower to manage git? It is a GUI app that allows robust git management. Anyone use it before? I like it but I am looking for additional thoughts.

[kristoffVillanueva]

For the tip#1, when you want to make sure you fetch all the changes happening in the remote master you can just do "git pull origin master" in the branch you are working. This is straightforward and does not involve more steps. Is there any disadvantage of doing this?

[_truthful_q_]

If you work at any reasonably sized organisation, they probably stopped using "master" for "main" more than a year ago.