Git vs. GitHub: What's the difference?
ฝัง
- เผยแพร่เมื่อ 8 พ.ค. 2024
- Learn more about Git Repos and Issue Tracking: ibm.biz/git-repos-and-issue-tr...
Explore DevOps and Git integrations in this free tutorial: ibm.biz/devops-and-git-integra...
Check out IBM Cloud Shell: ibm.biz/product-ibm-cloud-shell
Check out IBM Cloud Continuous Delivery: ibm.biz/ibm-cloud-continuous-d...
► Earn a badge with FREE interactive Kubernetes labs: ibm.biz/hands-on-k8s-labs
What is Git and what is it used for? What is the difference between Git and GitHub, or GitLab?
In this lightboard video, Nathan Hekman with IBM Cloud, answers these questions and much more by using an example of a media streaming company that has two developers who need to write code at the same time on the same code base without conflicting with each other in order to build a new music streaming app.
Get started on IBM Cloud at no cost: ibm.biz/sign-up-free-cloud-acc...
Subscribe to see more videos like this in the future → ibm.biz/subscribe-now
#Git #GitHub #GitLab - วิทยาศาสตร์และเทคโนโลยี
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.
Plot twist: the video is NOT flipped....he's just really good at writing backwards 🤣
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.
Simple, crystal clear with examples.. perfect 👌
some of the most informative prog/comp/IT videos on youtube, good work
I keep coming back to this channel for clear and straight-to-the-point information. Thank you for your explanation.
This is really simple, accurate, and flawless. Thank you so much
Nice and simple explanation Nathan, looking forwards to more.
I have learnt so much from this IBM series, thank you so much. Great explanations for so many topics
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.
You taught me Networking MMU 🫡
Oh thank you! You are amazing to explain it in such a simple way 🙂
This is very much to the point and easy to understand! Thank you Nathan!
Thank you for keeping this simple and easy to understand for new comers!
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.
Right?
Great job Nathan!!!! Seriously brilliant explaination.
Wow, THIS IS AMAZING EXPLANATION. I CAN'T THANK YOU ENOUGH.
Thank you Nathan, this video is really helpful for me!!!
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.
Superb explanation. If could you please give the actual demo, it would be great. Thank you.
Thank you!!! Someone who finally simplifies it! Great job!
Amazing, simple explanation. Thank you!
Excellent explanation. Very easy to understand.Thank you for the wonderful presentation also.
Thankyou so much for this clarity with clear example.
That was super helpful. Thanks man!!!
Coming off an Udemy course on the topic, this was a best revision recap. Absolutely the essence, straight to the point!
This is just simple - to - understand knowledge, Thanks Nathan!
Thank you so much man for simply explaining this
Nice and simple overview. Great work :) Thanks.
well to be honest, am impressed by his delivery of the concept in the difference between Git and Github
Thank you IBM to explain in a easy way. best explication about the git and GitHub without to much verbiage.
Explicit and well explained! Thanks.
thank you so much! the explanation is too good and simple.
Perfect explanation. crystal clear.
Best Explanation on YT...
This clip is extremely useful. You made an excellent job!
Thank you! We're glad you found it helpful! 👍
Excellent explanation. Want more video like this.
Great illustration!!! Thank you!!!
Simple and awesome explanation ☺️
Wooow explains dope crystal clear... Understandable 💯
Crystal Clear. Great Job.
brilliant explanation!
Very well made videos...please share more such content.
Well this video deff got me intrested in learning how to use it.
Thank you. A great video, as always!
Very well done!! Thank you Nathan
Just blown away by his ability to write and draw in reverse so fluidly 😸 lol
He is not:) it’s just the way video was recorded.
I didn't know Mr.Beast was so good at explaining tech concepts. Good job Jimmy.
this is awesome thanks for the video!
thanks .. i know have vids i can share to friends an family to help essplain what "we do". and why its so great..
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?
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
You got me at let’s git started !!
Crystal clear explanation. Any one can understand it. Nice.
♥
Thanks IBM for the video. I have a better understanding.👍🏼
thank you. its mindblowing. and great explanation.
Thank you Nathan, excellent overview and explanation :-)
Right into the point, Love this😍
Nice - that was a pretty good explanation.
Great explanation
That's are super helpful to visualize what's going on! Thank you!
Glad you liked our video format, Nate, thanks for watching! You can subscribe to our channel for more videos like this one.😉
Thanks for your information Sir
Deserves a like for sure
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?
thanks for the tutorial!
Great explanation Thanks !
I never understood why ppl called it PR, but now I can understand it, thanks!
Thank you Nathan . Good job :)
really Awesome... superb explination on Git and Github
4:20
that's what I wanted to ask thank you so much !
beautifully explained
Now thats a real good Video, thank you!
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.
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!!
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
great explanation
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.
A very nice & pretty well explanation 👏 👍
Hello good morning Nathan! I have watched your video regarding GIT, at present, I am a student of Data Analytics, can I use GIT as my repository for my studies? Thanks
Thank you sooooo much for this.
Nice!... Excellent teaching!
4:31
Thank you, I am Indonesian you was give me new knowledge.
Thanks, Nathan.
Thanks Nathan
Well presented Tx.
I wish i could like this multiple times
This is Awesome
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 ❤️
Great video!
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?
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
Simplicity 🙏
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 ?
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?
amazing video!
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?
Das Quietschen der Stifte bringt mich um, aber tolles Video!
so good man
Great video
wow thankyou mister man this are just great and im not able belive me eye ball that how great it are for me cuz im are new learn the hacker programmer coding engineering of the software and now im know what are the git that great thank you mister
I can't stop focusing on how good Nathan can write backwards
super helpful
If Nathan and Greg work on different branches there will be no merge conflict
Thanks. Quick question. How is code in Git repo put together and what is a build process?
Keep posting videos!
Haha, we will, Leo, thanks for the feedback! 😉 Be sure to subscribe to get notified about the new ones.
Great video😁.. I have a doubt does grey have to do all its work again after pulling the updated code
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.