What does 'git remote add upstream' help achieve?

I was reading on:

Here is an extract:

  • Git log output log file
  • git svn fetch & rebase broken after connection failure
  • Git - Switching branches (windows) & uncommited changes
  • What is the proper way to include a file once into a repository and then ignore subsequent changes?
  • Gerrit email notification for push to master branch
  • Git apply patch fails silently (no errors but nothing happens)
  • Your Repository Up to Date

    In order to get the latest updates from the development trunk do a
    one-time setup to establish the main GitHub repo as a remote by

    $ git remote add upstream git://github.com/diaspora/diaspora.git

    Rebase Your Development Branch on the Latest Upstream

    To keep your development branch up to date, rebase your changes on top
    of the current state of the upstream master. See the What’s
    git-rebase? section below to learn more about rebasing.

    If you’ve set up an upstream branch as detailed above, and a
    development branch called 100-retweet-bugfix, you’d update upstream,
    update your local master, and rebase your branch from it like so:

    $ git fetch upstream
    $ git checkout master
    $ git rebase upstream/master
    $ git checkout 100-retweet-bugfix

    [make sure all is committed as necessary in branch]

    $ git rebase master

    Why is adding a ‘remote upstream’ needed in this case? Coudn’t I have just done:

    $ git checkout master
    $ git pull origin master
    $ git checkout 100-retweet-bugfix

    [make sure all is committed as necessary in branch]

    $ git rebase master

  • how to use tags in GIT
  • Can not push changes after using git reset --hard
  • Push to github without password using ssh-key
  • Automatically reword all rebased commits
  • 502 Bad Gateway from Nginx for large GitLab fork
  • Configure bower to install only dist folder
  • 2 Solutions collect form web for “What does 'git remote add upstream' help achieve?”

    The wiki is talking from a forked repo point of view. You have access to pull and push from origin, which will be your fork of the main diaspora repo. To pull in changes from this main repo, you add a remote, “upstream” in your local repo, pointing to this original and pull from it.

    So “origin” is a clone of your fork repo, from which you push and pull. “Upstream” is a name for the main repo, from where you pull and keep a clone of your fork updated, but you don’t have push access to it.

    This is useful when you have your own origin which is not upstream. In other words, you might have your own origin repo that you do development and local changes in and then occasionally merge upstream changes. The difference between your example and the highlighted text is that your example assumes you’re working with a clone of the upstream repo directly. The highlighted text assumes you’re working on a clone of your own repo that was, presumably, originally a clone of upstream.

    Git Baby is a git and github fan, let's start git clone.