"... now I want you to imagine that some upstart new at the company has decided to just make edits on the master branch. Yep, those people do exist." This is where I cracked. XD
That was funny, but jokes a side, if I'll make changes in other branch, feature-d, and then merge it to master, wouldn't it have the same result as someone who made edits in master? For the next person that want to merge to master, wouldn't it be the same? Maybe it's just less safe? Help me out here😅
Me too. Ever since I made my own repo and have been consistently making changes to it, it has been getting easier and easier. I now am starting to understand different concepts. It is alot easier than I thought it was in my mind.
@The Net Ninja: I just found this tutorial when I was trying to understand a good workflow and common use case for branches and merging. And I must say you are one of my favorite RU-vid instructors in the way you explain everything step-by-step! Keep up the good work!!
I was so confused about how to resolve conflicts in files, VS Code also makes it a little more intimidating with different functions, messages and whatnot, but this helped me to understand what it actually all does, how it happens and how to resolve them. Thank you!
You are a truly gifted instructor! I recently purchased a udemy course on git and GitHub, however the explanations on it weren't that great. I'm probably gonna refund that course cos your course is so much better. And it's free! P. S. If you do make a udemy course on this I'd definitely purchase it
that little "upstart" damn him ! Touching things he's not supposed to ! anyway im glad he did otherwise you wouldnt have done a video on it ! thanks ninja really enjoyed it👏 ...." mumbo jumbo " 🤣😭🤣
"git branch" does the same as "git branch -a". i used to use "switch" instead of "checkout" to walk to different branches :) . plus, "git checkout -b " is equal to "git switch -c "
or you can merge it using bash and then after opeining that file using VScode and it will give 3 options apply local chnages apply remote changes Apply both This will come usually when you are facing these type of issue , Code in the master branch (which would be in remote) would be different or you can say step ahead of you .
So, if there are two people who've each made a branch to work on different features need to commit back to master because they're done with their features and they happen to have modified the same files, would that not be the exact same scenario? Wouldn't whoever happened to finish first become the "upstart" in the video despite doing it the way they were supposed to?
i have a question why don't you use git push after commit ? is it for educational matter or what ? thank you by the way for the videos they are perfect clear and straight to the point
On 2:48 mine shows merge made by the 'ort' strategy, upon searching on their documentation it says Ostensibly Recursive’s Twin which basically replaces 'recursive' strategy but faster.