[DOCS-5786] Advise setting the "upstream" repo in our github 102 tutorial Created: 07/Jul/15 Updated: 11/Jan/17 Resolved: 02/Mar/16 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | about |
| Affects Version/s: | None |
| Fix Version/s: | 01112017-cleanup |
| Type: | Task | Priority: | Minor - P4 |
| Reporter: | Akira Kurogane | Assignee: | Kay Kim (Inactive) |
| Resolution: | Incomplete | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: | |
| Days since reply: | 7 years, 50 weeks ago |
| Description |
|
In the github-102 tutorial page for contributors there is a step #2 ("Pull in changes made by others") we instruct to them to run:
This will fail if they have not set an "upstream" repository. We didn't instruct them to do so in the github-101 tutorial. Also I think it's an easy mistake to think you already did that or to think git does it automatically. I suggest the following addition, shown in red below, that links to the shortest github.com doc on how to do it. (2) Pull in changes made by others.Pull in changes made by others since you forked your repo and replay your commits on top. (See here for how to set an "upstream" remote if you have not already done so.)
The operation “replays” your work on top of the commits that have happened since you began. For more information, see http://git-scm.com/book/en/Git-Branching-Rebasing. |
| Comments |
| Comment by Akira Kurogane [ 02/Mar/16 ] |
|
No worries. |
| Comment by Akira Kurogane [ 02/Mar/16 ] |
|
Well, this was here for quite a while. Time to chuck it. |