Skip to main content

GitKit (VSCode Edition): Learn git and GitHub in Context

Grant Braught, Lori Postner, Darci Burdge, Ruth Lamprecht, Stoney Jackson, Karl R. Wurst

Section 4.3 Verifying the Upstream Remote

When you open a fork in GitPod, GitPod clones its repository. This creates a remote named origin that points to the repository it cloned. When you clone a repository, this is typically the only remote created automatically. But GitPod goes a step further. It also creates upstream remote that points to the repository that your origin forked from.
Like the last activity, you will be working within the KitClient for this activity.

Exercises

2.

To synchronize your fork, you will need to use this upstream remote. First, let’s confirm that GitPod correctly created the upstream remote. This exercise will walk you through that process.
(a)
The git remote -v command lists the names and URLs of all of the remote repositories (or just remotes for short) that your local repo knows about. Run this command in the directory that contains your local repository.
(b)
Confirm that upstream points to the upstream project on GitHub. How did you confirm it?
(c)
    The upstream remote provides your local repo with the information it needs to find the upstream repo. In git this information is represented using a URL. How is this information represented in Figure 4.1.1?
  • It is labeled as "origin".
  • It is labeled as "upstream".
  • Correct! The diagram shows your upstream remote on the top right side with the label "upstream".
  • It is labeled as "local".
  • It is labeled as "feature branch".
Hint.
When you issued the git remote -v command pay attention to the name given to second set of fetch and pull URLs.
You have attempted of activities on this page.
PrevTopNext