Git vs. GitHub: What's the difference?

[@vedkorla300]

I didn't know Mr.Beast was so good at explaining tech concepts. Good job Jimmy.

[@Insain71]

I been learning git and github following directions but not fully understanding what I was doing. After watching this video I understand exactly what I was doing and have more of an understanding to start building some projects with git & github. Thank you for the illustrations they really help.

[@walKyism]

4yrs and this explanation vid still killing it on the essentials

[@andresalvarez7303]

Plot twist: the video is NOT flipped....he's just really good at writing backwards 🤣

[@alejandroperez5368]

Plot twist: he's not writing on a transparent acrylic in front of him. He's not even depositing ink. It's all CGI

[@Gonagaoa]

He rotated the screen, seethe watch in his hand, it's in right

[@codewithsusan]

😂

[@sanctioned.ayusharma]

Plot twist: There's no plot twist...

[@warplanner8852]

It's all done with smoke and mirrors.. ..well, mirrors only.

[@sathya-enjoy_lifetothefullest]

Simple, crystal clear with examples.. perfect 👌

[@MrEvansjethro]

Thank you Nathan and IBM Technology for the great content. You guys put a lot of effort to make things easy for us to understand. Keep up the awesome work.

[@mjp96]

Right?

[@iconeers]

well to be honest, am impressed by his delivery of the concept in the difference between Git and Github

[@colorfuljosh]

some of the most informative prog/comp/IT videos on youtube, good work

[@yatin1370]

Coming off an Udemy course on the topic, this was a best revision recap. Absolutely the essence, straight to the point!

[@TrKaris]

This is by far the best among the many videos I've watched to get the basics of Git & Github. Keep up the awesome and simplified explanations.

[@francis_tech]

You taught me Networking MMU 🫡

[@nmartin32950]

Excellent vid. Just some quick questions which are probably obvious to everyone else: 1) How does Greg know a PULL-MERGE is required, did a PUSH attempt fail? 2) Does Git interrogate and analyze the code inside the file and highlight the specific conflicts or is it just file name, file size and timestamps? 3) Does GitHub/Lab automatically push a notification to whom ever is responsible for answering the PULL-REQUEST? 4) Is there a part two vid clearing up the Greg stages of interaction with the main branch?

[@adalovelac24]

did you find answers ?

[@semihozkan8514]

@@adalovelac24 did he/she find answers?

[@adebiyial]

I can help you here. 1. Greg can tell if he has to pull the code from the main branch by checking the GitHub repository to see if there are new changes. Or, more ideally, if Greg tries to push to the main branch, GIT is smart enough to know that there is a conflict. So GIT will say something like: Greg, you are trying to push your changes to the main branch but the main branch has some changes you don't have. Please pull first before pushing. 2. Git does a lot of things to check if there are changes. Take two files for example, A and B. As long as they are two different names, there is no similarity even if they have the same content. If they have the same name, GIT can check it's own copy (usually the latest copy) and cross check the new copy. It checks line by line. If both files have the same content, then nothing changed, if they don't, GIT will show you something called a "diff". A diff is just GIT telling you the difference between each line of code. If line 1 of the file GIT has is different from line 1 of the file Greg is trying to merge, GIT will tell Greg: There's a conflict. 3. PR has their own rules. Ideally, you as a user that started or opened a PR can choose to notify someone to take a look at it, or you can leave it there until the person comes to check. It's all about notifications, no hard rules. That's not GIT's responsibility, it's GitHub.

[@srlhyo]

@@adebiyial but buddy, here is one thing it wasn't clear to me: "knowing there is a merge conflict from pushing the code and git telling there's new code on github I don't have, is making a pull request a way to avoid dealing with the merge conflict? I mean, if I make a pr then I don't need to bother pulling any changes?

[@iaphlnt]

@@srlhyo A pull request isn't going to resolve any conflicts, you still have to do that yourself. The only thing that can happen is you pull and handle the merge locally or force a push and delete any changes that were made, probably not a good thing to do

[@carsten2600]

I never understood why ppl called it PR, but now I can understand it, thanks!

[@conceptrat]

Just blown away by his ability to write and draw in reverse so fluidly 😸 lol

[@makeurmoneyeasy]

He is not:) it’s just the way video was recorded.

[@TonyJose9162007]

I wonder how you people have matched Hekman's hand movements with the writing in inverse on the screen. I find this technology truly amazing !! I MEAN WOWW!!

[@AP-eb8hd]

the concept of lightboard works on special glass... used for writing and then mirrors to invert the image.

[@AP-eb8hd]

Or you can software to reverse.. if its not online real-time streaming

[@asritakinipulu3821]

I keep coming back to this channel for clear and straight-to-the-point information. Thank you for your explanation.

[@rahulborade7533]

This is just simple - to - understand knowledge, Thanks Nathan!

[@landertee]

I can't stop focusing on how good Nathan can write backwards

[@B2STisBaCk]

This is really simple, accurate, and flawless. Thank you so much

[@pmpmersal9375]

Your videos are very useful for me. But, allow me to add one note. You write the notes in two colours, one is bright and clear for me. While I have a problem with the other colour. Thanks again and I am sorry for the out of subject note.

[@MANISH-Dev]

Best Explanation on YT...

[@edwindersingh9300]

Nice and simple explanation Nathan, looking forwards to more.

[@dipan246]

Superb explanation. If could you please give the actual demo, it would be great. Thank you.

[@popedavid6668]

Thank you!!! Someone who finally simplifies it! Great job!

[@Deployer]

Thank you IBM to explain in a easy way. best explication about the git and GitHub without to much verbiage.

[@johannes.sbw-media]

If Nathan and Greg work on different branches there will be no merge conflict

[@alok4002]

Crystal clear explanation. Any one can understand it. Nice.

[@ladaroni9588]

♥

[@josephthecreator]

Thank you for keeping this simple and easy to understand for new comers!

[@Tooxcade]

Wow, THIS IS AMAZING EXPLANATION. I CAN'T THANK YOU ENOUGH.

[@kavon9748]

Oh thank you! You are amazing to explain it in such a simple way 🙂

[@julietteugoh]

I wish i could like this multiple times

[@ashishkamble8833]

You got me at let’s git started !!

[@Userk2406]

Great job Nathan!!!! Seriously brilliant explaination.

[@milanturkey]

Das Quietschen der Stifte bringt mich um, aber tolles Video!

[@shyunuw]

This clip is extremely useful. You made an excellent job!

[@IBMTechnology]

Thank you! We're glad you found it helpful! 👍

[@kalyanb2002]

I love the content shared by IBM cloud. The tit bit video's make the concept simple to understand . Thanks to Nathan and all greats who help spread knowledge.

[@bayesian7404]

Nathan, Great job. Plus I also bluegrass so that gets u another star. In comments Singh Noah asked a critical. Read Anton T wrote a very informative reply. While I do not use IBM Cloud, they do provide excellent tutorials.

[@88gurlygurl]

Nice - that was a pretty good explanation.

[@DavidDavida]

thanks .. i know have vids i can share to friends an family to help essplain what "we do". and why its so great..

[@NaveenKumar1611-m1v]

Thankyou so much for this clarity with clear example.

[@lucid1963]

Excellent explanation. Very easy to understand.Thank you for the wonderful presentation also.

[@zenrobotninja]

I have learnt so much from this IBM series, thank you so much. Great explanations for so many topics

[@abnerandreymartinezzamudio3366]

I can't believe there are people who are passionate about these things

[@laaven]

Well this video deff got me intrested in learning how to use it.

[@Jay2Ops]

Thanks IBM for the video. I have a better understanding.👍🏼

[@jaqueann3280]

Wooow explains dope crystal clear... Understandable 💯

[@brotendo]

Is ability to write mirrored is amazing

[@hlebuska9434]

Amazing, simple explanation. Thank you!

[@xinyujiao4464]

When Nathan changed the main branch, it was called "push". Why then, when greg wants to make changes, it is called a "pull request"?

[@anton_t]

You clone a repo only once, in the very beginning of your work. Both Nathan and Craig cloned the Repo. Then Nathan pushed his changes, but basically he was supposed to pull and merge first, to make sure Craig hadn't already pushed his changes first. So in GIT you do the CLONE action only once - that's how you download the whole huge repository on your local machine. And then whenever you need to make a change, you first PULL the current version (and when you do that only the changes are downloaded, not the whole repository). Then you commit your own change to the branch you have and then you PUSH it to the server/cloud. And until you have finished your PUSH action the system is locked for all the other developers - they cannot commit or push anything until you're done. As soon as you are done pushing (lol) the system gets unlocked again and someone else can do his/her own PULL-COMMIT-PUSH.

[@magansingh8842]

Submitting a pull request means, Greg is requesting others to pull and give a response (approval or denial) on the new home screen having both Bluegrass and Rock features.

[@natek3954]

@@anton_t thank you for response this really clears things up for me!

[@conceptrat]

A “pull request“ asks a repo/project to “pull“ changes you've made on your cloned repo into theirs and “merge“ them. This is different to a pull which does a “fetch“ and either “merge“ or “rebase“ from a repo.

[@bayurahmanadinata3815]

Thank you, I am Indonesian you was give me new knowledge.

[@Cos_Wayne]

This is very much to the point and easy to understand! Thank you Nathan!

[@shrutijadhav552]

Great explanation

[@varunaws4432]

really Awesome... superb explination on Git and Github

[@MichaelKssf]

4:20

[@taha7shaikh]

Thank you so much man for simply explaining this

[@itsmemasud]

he explained so nicely

[@natek3954]

That's are super helpful to visualize what's going on! Thank you!

[@IBMTechnology]

Glad you liked our video format, Nate, thanks for watching! You can subscribe to our channel for more videos like this one.😉

[@duroskylala]

Nathan, I have a question on this video. At the end of your example, why did you do a Push and not a Pull and Merge?

[@lyeejiun99]

Thank you Nathan, this video is really helpful for me!!!

[@SilentSolution]

Thanks for your information Sir

[@ETI-edu]

Great explanation Thanks !

[@boldschool6308]

Deserves a like for sure

[@swapnilkulkarni6719]

Very well made videos...please share more such content.

[@raufmasoumi]

thank you so much! the explanation is too good and simple.

[@jennwng]

Great illustration!!! Thank you!!!

[@tusharg2751]

Perfect explanation. crystal clear.

[@samreet101]

That was super helpful. Thanks man!!!

[@letsgodevs]

Can you do blockchain video Not the basic Just like zkp , IPFS , how wallet actually work , rules of blockchain development ( longest blockchain rules , POS And ect ...) .... So i would be great for me and my university students By the way thank you very much fir this great explain ❤️

[@hidayahBasir-p3u]

brilliant explanation!

[@Tony25287]

Thank you. A great video, as always!

[@thanurarukshan6696]

Right into the point, Love this😍

[@TheFonix456]

Good job Greg

[@mzkhan1576]

thank you. its mindblowing. and great explanation.

[@596rochak]

Quick question, could Greg have been able to do the same with a Push request ? When should one do a git Push vs a git pull request ?

[@dheerajgupta15]

Following.

[@subbamaggus1]

@@dheerajgupta15 my expirience is that greg and nathan push their branches to the main repo. so that both info is there in gitlab/github. and then you create a pull request (so everything is done on the server). afterwards you merge the main branch to your local repo, and then push. and create a second pull request on the main repo. sounds right?

[@IBITZEE]

Nice video... good info... but "CLI vs Web" should be "Local vs Web"... I can work on the web with CLI tools... and when you are explaining creating a branch... maybe you should add some more info on how that branch is stored locally... and how is stored in the web (if you are using GH/GL/...) same for the pull-request... and what happens at storage level... ;-) valuable videos... keep them comming...

[@tigrayrimey6418]

Explicit and well explained! Thanks.

[@MDHOSSAIN-gj5ve]

Excellent explanation. Want more video like this.

[@MrHav1k]

Very well done!! Thank you Nathan

[@ObaidahNaseer]

I think I git it now

[@AugustsBeta]

😂

[@g9super]

Simple and awesome explanation ☺️

[@RajeshMenontechnospirituality]

Thanks, Nathan.

[@abdullahnaveed4834]

great explanation

[@nihalbahadir4262]

Thank you Nathan . Good job :)

[@protectiondata7783]

that's what I wanted to ask thank you so much !

[@semtex6412]

top-man Nathan! thanks for the vid. so you know Billy Strings, eh?

[@mihisarakaveesha8954]

Crystal Clear. Great Job.

[@tekwevera1049]

Thanks Nathan

[@cuddy90210]

Nice!... Excellent teaching!

[@MichaelKssf]

4:31

[@Milka-br1xw]

Now thats a real good Video, thank you!

[@hiteshsuthar1097]

Simplicity 🙏

[@TheGloriousRussian]

I'm a little bit confused why for Greg it's called Pull Request but not Push Request isn't he is pushing his changes to the GitHub repository as Nathan did before?

[@jeepgc3530]

Thank you Nathan, excellent overview and explanation :-)

[@JosePayano]

Thanks Natham! Truly appreciate the straightforward way you use to explain what otherwise would be a complex subject... MY QUESTION: Which, I think you didn't mention is 'why are these platforms called "GIT"? I don't see any related meaning to 'Version Control Systems'. What exactly is the origin of the Acronym?

[@IBMTechnology]

According to Wikipedia... Torvalds sarcastically quipped about the name git (which means "unpleasant person" in British English slang): "I'm an egotistical bastard, and I name all my projects after myself. First 'Linux', now 'git'." en.wikipedia.org/wiki/Git#Naming

[@Sumanth_Siddareddy]

A very nice & pretty well explanation 👏 👍

[@rmmm3000]

thanks for the tutorial!

[@MS-xp4vt]

This is Awesome

[@CHRISUJI_]

this is awesome thanks for the video!

[@RB-lc8lh]

I couldn't focus on what he was saying as I was too fascinated by the lightboard technology that made it look like he was writing backwards. 😲

[@AJKirby64]

Wow. Just 30 seconds in you insert ear destroying squeaks. Who knows if the rest of the video was any good but I have learnt that IBM for all its brilliance can't control painfully loud feedback.

[@digitaldevilstv4896]

Thank you sooooo much for this.

[@M1gas]

please consider removing those high pitched sounds from the market on the glass. its painful. Thank you so much fior the video!

[@PattyJames3478]

Great video!