Git Source Control For The Impatient

[@hamidjade]

I have watched quite a few of your videos and it is amazing how such a simple format (dude sitting and talking with no fancy intros and effects) can be so valuable. You are absolutely rocking it and out of 15 videos 15 have been 100% valuable information and 0 BS. My only wish for christmas is that anyone interested in linux or anything you cover end up on a path that leads directly to you, without any detours. What a huge timesaver this would be for mankind! THANK YOU!

[@hamidjade]

You tear down the "hit subscribe and like this video" bs trend that is going on. Not once have I heard you say such a thing and the absolute first thing I did was hit sub and turn notifications on. I will try to remember to like all of them also! This channel is GOLD people! GOLD!

[@EngineerMan]

Thanks for the kind words, I'm glad you enjoy this style of video. I'll keep doing my best to create good content for everyone :)

[@carlvk1893]

Man you rock. Best git tutorial I've encountered.

[@hosnymubark6528]

Thats right!

[@TornTech1]

other people has posted this, but id like to repeat it for maximum impact :P... could you extend this video with an additional one detailing how to do pull requests and how you might track changes against an issue.... This will help people who might want to start contributing to opensource software which usually don't allow direct commits to master. you could go totally wild and extend this into a series about how you set up commit rules so you cant merge to master unless the CI pipeline build is passing and its had 1-2 people code review... that is what will properly represent how its working out here in industry! Love the tutorial though! Currently a TFS user, but totally moving my sorry ass over to git!

[@shivamrastogi3154]

Hello, if you have found any Playlist which caters to that please share. I am in a great need of it. Thanks

[@shikhanshu]

it doesnt get better than this.. this channel is the best there is

[@Knee-Lew]

same here, I got easily understand the explanation of git in a simplest way. now I know how to branch a git, instead of relying on a master branch.

[@ApiolJoe]

Oh boy! thank you for this! I wanted to start learning to vc my projects -how small they may be) with git just to start learning good practices. However I'm super busy and I couldn't not find a quick and clear tutorial about it, meaning my start with git was dragging on and on... This video is absolutely perfect, this'll get me started!

[@rebootlinux608]

This is honestly the best tutorial I have every seen for learning git/github.

[@michaelangellotti5741]

I wish I found this first. Your presentation style is perfect for my twitchy learning issues.

[@NubmerSeven]

Man you're the best. Really. And youtube has maaaaaany people explaining these things.

[@EnglishRain]

Impatient people accross the globe thank you!

[@stoianandreimircea1509]

You get me:) I congratulate you on your videos...you really think like an engineer and do not skip steps for us little ones. Just makes me want to be as bad ass as you:) I hope one day I get to a level that I can colaborate with you. Hugs from NZ

[@AlexFraundorf]

Excellent intro to Git. I wish it had been available when I was first learning it. Thanks!

[@tojtowny]

One of the clearest explanation of the github. Cheers.

[@timetorelaxfocus9642]

You broke it down well. The only other thing I wanted to see is reverting to a previous change. Thanks

[@SurajPillaiOne]

Nice and informative video. I would request that you also take some time to talk about having proper commit messages. People learning the basics without the etiquette are how we end up with repos with 1000s of "Made Changes" commit messages. Defeats the purpose of using git, IMO.

[@dilshand.5127]

All under 16 minutes, thank you EM!

[@MegaAkash123456]

Man you're dope! Saw your Craigslist scam video and immediately subscribed, savage af!

[@EngineerMan]

Thanks!

[@jgilmourtechsmog]

Nice job. I’ve always done pushing to git solo and wondered how to collaborate with others so this is really cool!

[@ShreksSpliff]

Thank you for ssh, that password was annoying. Great content, right at ny level. Ty xx

[@timmytim9054]

I like that when you explain, you speak in plain english

[@paulm3702]

I dont git it

Finally I git it.

[@Knee-Lew]

git a grip!

[@yusy4code]

Hey, I think it is the best representation which covers at most stuff under 16 mins. Thanks for that. Just curious, in your last example of change1 and change2 branch, can we see the changes of other people. I mean when you type git status, it shows master and change1 on one terminal but it didn't show change2. Is there a way to see other branches as well.

[@robinw77]

The branch would be visible once the other person does a push, then you do a GIT FETCH (rather than PULL). After that you would be able to GIT CHECKOUT CHANGE2 and see the other person's changes.

[@yusy4code]

Thank you for replying. Appreciate ur help.

[@ShreksSpliff]

Git out

[@FirstLast-hm8oz]

Well done. Thanks a lot. It makes my live easier.

[@StevenLynn]

I needed this video about two weeks ago trying to troubleshoot something and forgot git commands.

[@jpScarfac3]

Very concise and easy to understand. Thanks.

[@nolifeorname5731]

Very nice, maybe it would also be anice video idea to discuss issues and pull requests on github itself?

[@сойка-и8й]

The repo cool project had 3 branch master, change1 change2, but in ur pc you were seeing only 2 master, and change1 , while in friend repo we see master change2, what if I want to checkout change2, bcoz it showing only 2 branches in my pc ???

[@binbashbuddy]

Try git -am "commit message", it adds and commits at the same time. I've used git for quite a few years now, I set up a repo on a machine at work where we can all push and pull to dev and then pull to production when ready. You don't actually need github to do this, especially if you're working on private code and don't want to flip github any bucks.

[@kirtipandya4618]

Thank you very much for such a nice explanation. There are three branches. 1) master 2) change1 3) change2 What if I want to see what’s going on in all three beaches? Can we see that? Thanking you in advance.

[@EngineerMan]

You cannot have more than one branch checked out at any given time but any branch can be diffed against any other to see what's different.

[@kash1222]

Good video! I prefer git rebase in order to prevent a merge commit. Also git diff seens missing? And never do git add -A, of git commit -a. It could very well commit unrelated changes. Last, git add -p is super!

[@EngineerMan]

Just for the benefit of anyone who reads this comment, git rebase on a shared branch is how chaos is created since it alters history. git rebase has its purpose but it's definitely not a substitute for git merge.

[@kash1222]

@@EngineerManRebase does not change history. It changes the commit on which a branch "would have" branched, i.e. places commits from your branch on top of missing commits from master. Furthermore, I never said rebase would be a substitute for merge. It does however provide a way to keep your commit-history clean.

[@arielspalter7425]

Excellent tutorial!

[@fadiliabdeljalil770]

Very cool tuto, thank you very much!

[@benjaminrice9551]

Thanks, great video, it was super helpful.

[@shorts-hc7uz]

Thanks it is helpful exactly what I wanted

[@fernandogaray1681]

This is pure gold

[@ardenthebibliophile]

Makes a lot of sense, but now a couple of questions! What would have happened if you merged master into change1? Would it have overwritten change1? Would you be willing to show some of the GitHub side of things? My company also uses BitBucket which, as I understand it, is very similar. If there are others maybe a compare and contrast would be nice. Appreciate the straightforward explanations! Btw do you use or prefer any IDEs for python?

[@harleyspeedthrust4013]

If you merge master into change1, the same rules apply as merging change2 (or change1) into master: git will try to merge them automatically, and if there are conflicts you will have to resolve the conflicts manually. I don't know about BitBucket but I do prefer the github UI for pull requests and merging into master. At the company I work for (and at most competent companies), if you make changes to a codebase you need to create a pull request and go through code review. A pull request is a request to merge your branch into master, usually with an explanation of the changes you made. In many cases, opening a pull request on a company's repository will trigger automated tests to run, and these will give either a green check or a red X next to your pull request (indicating if it's going to break anything when you merge). You also need to request someone to review your pull request and the changes you made, and you may also need to get quality assurance on your pull request

[@jeff9576]

i really needed this ty

[@sbiefeni1]

Great stuff. how about javascript closures?

[@mayur9876]

Thanks for the video.

[@flipthecoin.]

awesome content.

[@juan-ou3gq]

you are the Best!

[@chilusoftcorp7762]

Hello Engineer man. Can you do a Angular 6 tutorial

[@hik4ru]

Nice presentation, really basics oriented but clear as cristal. Thanks! (but why nano :O )

[@gandsnut]

Any opinions on Microsoft buying GitHub? Aside: somehow I thought Linus Torvalds was behind GitHub, but some quick Wikipedia corrected that, where now I know he originated Git. Thank goodness I didn't have to drive to some library to figure this out.

[@EngineerMan]

A lot of people are upset by that move. I personally don't care because I don't have anything private on GitHub.Linus Torvalds originally created Git specifically to provide source control on the Linux kernel.

[@theburntcrumpet8371]

This is probably a super noobish question, but why "git add -A" and not "git add ."? Just wondering, I've been using the latter for a couple of years and it's not really caused an issue

[@EngineerMan]

If you're using Git version 2 then those two commands are identical.

[@zenmaster24]

could you go in to `git rebase` and when to use it please?

[@Axzuma]

How do you deal with simultaneois branches that need to be merged into master? Example: imagine branch1 is a new version and branch2 is a priority bug fix. Branch2 gets merged into master and after a few days you're done with the new version on branch1 and want to merged it into master. What's the best way to do this?

[@EngineerMan]

You would just merge branch1 into master. Unless branch2 modifies the same stuff branch1 does, git will happily merge it without issue.

[@Axzuma]

@@EngineerMan Thanks for your reply. In the event both branches modify the same code you need to do a manual merge like the one you showed. Is that it?

[@drewbell5260]

awesome. thanks!

[@parthaprateempatra4278]

nice content

[@kamalhm-dev]

what is this os?

[@bruh_5555]

AMAZING

[@sputniq2828]

Yeah this rules. Thank you. Confused though, you told me chrome was the worst browser

[@EngineerMan]

This video is pretty old.

[@md9936]

great video but why you use nano instead vim ?

[@justChuka]

git it?

[@steveestrada7539]

How can i get hack into instagram account my brother passed away and my mother n i want to delete his profile for closure can u help? Thanks in advance

[@EngineerMan]

I would advise getting in contact with Instagram to get your brother's account removed. This will be quicker and easier.

[@steveestrada7539]

@@EngineerMan i did but they askrd to verify with his email and we dont have his email password

[@EngineerMan]

This may help: help.instagram.com/264154560391256

[@UniverseGOD2525]

git gud

[@mikewilson0]

What kind of n00b works as root? 😂

[@EngineerMan]

There was a lack of elitist comments on this video. Thanks for fixing that.

[@noweare1]

@@EngineerMan LOL, yeah, no shortage of that shite in technology.

[@krisnelson3932]

Excellent video, doing the side-by-side changes was a great idea. Thanks!