You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: book/03-git-branching/sections/remote-branches.asc
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -39,7 +39,7 @@ image::images/remote-branches-2.png[Local and remote work can diverge.]
39
39
To synchronize your work, you run a `git fetch origin` command.
40
40
This command looks up which server ``origin'' is (in this case, it's `git.ourcompany.com`), fetches any data from it that you don't yet have, and updates your local database, moving your `origin/master` pointer to its new, more up-to-date position.
41
41
42
-
.`git fetch` updates your remote references
42
+
.`git fetch` updates your remote-tracking branches
43
43
image::images/remote-branches-3.png[`git fetch` updates your remote references.]
44
44
45
45
To demonstrate having multiple remote servers and what remote branches for those remote projects look like, let's assume you have another internal Git server that is used only for development by one of your sprint teams.
0 commit comments