Skip to content

Commit a7a5c67

Browse files
authored
Merge pull request #86 from nturaga/gh-pages
Explain usage of the **upstream** keyword
2 parents 25ee421 + d060a9c commit a7a5c67

File tree

1 file changed

+6
-2
lines changed

1 file changed

+6
-2
lines changed

_episodes/03-sharing.md

Lines changed: 6 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -118,13 +118,17 @@ Branch master set up to track remote branch master from origin.
118118

119119
The nickname of our remote repository is "origin" and the default local branch name is "master".
120120
The `-u` flag tells git to remember the parameters, so that next time we can simply run `git push`
121-
and Git will know what to do.
121+
and Git will know what to do.
122+
123+
Pushing our local changes to the Github repository is sometimes referred to as "pushing changes `upstream` to Github".
124+
The word `upstream` here comes from the git flag we used earlier in the command `git push -u origin master`.
125+
The flag `-u` refers to `-set-upstream`, so when we say pushing changes upstream, it refers to the remote repository.
122126

123127
You may be prompted to enter your GitHub username and password to complete the command.
124128

125129
When we do a `git push`, we will see Git 'pushing' changes upstream to GitHub. Because our file is very small, this
126130
won't take long but if we had made a lot of changes or were adding a very large repository, we might have to wait a
127-
little longer. We can check where we're at with `git status`.
131+
little longer. We can check where we're at with `git status`.
128132

129133
~~~
130134
$ git status

0 commit comments

Comments
 (0)