I learned a lot from your excent tutorial, important details covered for people that don't know the endless acronmyms, terms etc. that often get skipped over. Great sound & pace Thank you..!
Yes, you can set the original as upstream and rebase with the original. from stackoverflow.com/a/7244456/9357244 : # Add the remote, call it "upstream": git remote add upstream github.com/whoever/whatever.git # Fetch all the branches of that remote into remote-tracking branches, # such as upstream/master: git fetch upstream # Make sure that you're on your master branch: git checkout master # Rewrite your master branch so that any commits of yours that # aren't already in upstream/master are replayed on top of that # other branch: git rebase upstream/master
Great video, would like to know how testing would be performed, say the person updated the a func that is calling some internal api which is not accessible from that person's local system. So in such cases will owner need to test the change and then merge the request ?
if the original repository is updated (either there's a merge or updates by the maintainer of the original repository), will other repositories that fork from this repository will get updated of the changes as well on their local repository?
Hey Rafa! The GitHub videos on youtube a shortened, concise version of the actual course. TheCodex course on Git and GitHub covers a lot more content in-depth :)
Always remember we must repent of our sins (sin is transgression The Law Of Yahuah The Father in Heaven. The Law are The Books: Genesis, Exodus, Leviticus, Numbers, & Deuteronomy). We must repent of our sins and Have Belief On Yahusha The Messiah. HE Died and Rose three days later so that we can be forgiven of our sins! Come to HIM
Brand new Git and GitHub Course for Beginners now on TheCodex! Check it out here: thecodex.me/courses/git-and-github
I learned a lot from your excent tutorial, important details covered for people that don't know the endless acronmyms, terms etc. that often get skipped over. Great sound & pace
Thank you..!
You explained it so well and clearly! My teacher did the same topic for an hour and after that, I was still confused. Thank you so much!
So true 😂 even our teacher took more than an hour and couldn’t explain . This is awesome 👏
looked 100 of tutorials and your series of git hub tutorials is accepting my brain.
MVP. Thanks for adding in Fork vs Branch at the end. I was going to go look for it elsewhere.
You are awesome bro. Simple and precise
Thank you for detailed video, and explanation of difference between branch and fork at 07:00. I appreciate that. Good work.
That was very informative and gave a clear understanding !!! Thanks a lot man!!!!!!!🤩
excellent explanation bro. Thanks for the info
thanks for this very useful tutorial
Thank you, this helped.
Hello!, if the original repository get updated with new commits or branches, can I update the fork with the new changes? Thank you in advance.
Yes, you can set the original as upstream and rebase with the original. from stackoverflow.com/a/7244456/9357244 :
# Add the remote, call it "upstream":
git remote add upstream github.com/whoever/whatever.git
# Fetch all the branches of that remote into remote-tracking branches,
# such as upstream/master:
git fetch upstream
# Make sure that you're on your master branch:
git checkout master
# Rewrite your master branch so that any commits of yours that
# aren't already in upstream/master are replayed on top of that
# other branch:
git rebase upstream/master
Thanks, it did help me make my first pull request. The starting point to collaborating to open source projects
Great video thank you.
THANK YOU! Exactly what I needed.
Crystal clear. Thanks man!
Very well explained
finally the video i was looking for!!!
Great video, would like to know how testing would be performed, say the person updated the a func that is calling some internal api which is not accessible from that person's local system. So in such cases will owner need to test the change and then merge the request ?
thank you this was very helpfull and good explained
if the original repository is updated (either there's a merge or updates by the maintainer of the original repository), will other repositories that fork from this repository will get updated of the changes as well on their local repository?
Nice and clear thank you for this
excellent explanation!
Thank you!
Great and well explained video!
Thank you brother, very much !
awesome video! thx!
good one
Hey Avil! Great Video, what are the differences between this videos and the one on your page?
Hey Rafa! The GitHub videos on youtube a shortened, concise version of the actual course. TheCodex course on Git and GitHub covers a lot more content in-depth :)
Clear example, thanks
amazing thank u
The fork button is not enabled in my repository.
Solid explanation!
Thanks a lot for this. Very nice tutorial :)
Thanks
When any changes/updates made to master branch will that be merged to fork automatically?
if the changes in the fork are committed and pushed to the master branch of the fork then yes.
Difference btw forking and cloning??
nailed it !
Awesome video ... Thank u so much for this video :-)
Can i have a repository which cannot be accessible by anyone except specific people ?
Killaken is absolutely right - You can create a private repo that no one can view except your collaborators.
What if i want to fork my file or code in a repo
this is a great video. You should try and contribute to Traversy Media in order to pull more traffic :)
great
how do I do that with the command line?
👍👍❤
Always remember we must repent of our sins (sin is transgression The Law Of Yahuah The Father in Heaven. The Law are The Books: Genesis, Exodus, Leviticus, Numbers, & Deuteronomy). We must repent of our sins and Have Belief On Yahusha The Messiah. HE Died and Rose three days later so that we can be forgiven of our sins!
Come to HIM
For fork sake.
defs not for non native English speakers..
No
I am non native and I understand it very well
@@talkingbirb2808 congratulations
@@talkingbirb2808 same