Git Tutorial 03 – Pushing & Pulling

In the last video, we just looked at adding files and commiting changes. This is great, but remember that in Git, commits are local. In this video we look at how we can set up remote repositories that we can push data to, either to use as backups, or for sharing with others.


I cannot believe I messed up the remote path that many times! I am sorry about that. Of course, the side effect is you learnt how to both add and remove remotes. So yeah… I did that on purpose.

At this point, we can create a project or join an existing one. We can add files and commit changes. We can push our changes to remotes, and fetch changes that other people have made. This is all great. However, we haven’t touched on one of Git’s most powerful features. I am of course talking about branching and merging. This will be the priority for the next video.

Again, any feedback is much appreciated.

Published by

Michael Marner

My name is Michael, and this is my website. I am currently working as a Research Fellow at the University of South Australia's Wearable Computer Lab. I am also the chair of the board and an announcer at Adelaide based community radio station Three D Radio 93.7FM.

3 thoughts on “Git Tutorial 03 – Pushing & Pulling”

  1. Hello,
    Tky for your videos on GIT, that’s really helpful ( I am completely new with this kind of tool ). There’s one point missing I think…What about getting back( and for ) to a previous commit localy?
    I think you should publish your videos on a website like ( great website with a lots of really cool videos on python…), you will get a lot of feedback.
    Tks again from a french houdini user!

  2. Hey Mate

    Yes, there are a couple of things missing from my Git videos at the moment. The three really only give you the bare minimum you need to work with Git. I plan on doing at least one more that will look at branching and merging. But yes, explaining how to revert back to a previous version will be important.

    Thanks for the feedback!

  3. Pulling vs. fetching. What’s the difference? Is one preferred?

    Same for merge vs. rebase.

    Are these different ways to skin the (same) cat?

Leave a Reply

Your email address will not be published. Required fields are marked *