Git vs. GitHub: What's the difference? 

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

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

😂

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

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

You taught me Networking MMU 🫡

Right?

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

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

♥

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

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

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

4:20

did you find answers ?

@@adalovelac24 did he/she find answers?

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.

@@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?

@@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

4:31

Following.

@@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?

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

Hey! Glad you enjoyed the video! 🙂 As for the making of, we explain it all in our "Community" section 👉 ibm.co/37r6z8h 🧐

No. He just has to resolve merge conflicts which will be visible on Greys' code. He can keep all , some and none part of the pulled code.

@@username-1043 Also due note, that just because you make a Pull Request (PR) doesnt mean it will get accepted. It can be denied for any reason. It will get denied by whomever is in charge of overseeing the github project. I say this, because some people have the sense of belief that they can just put up any code they want. which is not true. It goes through an approval process first.