Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add a git fetch exercise? #420

Open
jangari opened this issue Jun 27, 2017 · 3 comments
Open

Add a git fetch exercise? #420

jangari opened this issue Jun 27, 2017 · 3 comments

Comments

@jangari
Copy link

@jangari jangari commented Jun 27, 2017

Every time I teach this, participants ask how they can check to see whether origin has been updated before they try to git push so as to know in advance whether they're going to have to merge anything, or more generally just to compare their latest committed version with origin.

Is it worth adding a small exercise showing git fetch, and then how to compare master with origin/master?

@naught101
Copy link
Contributor

@naught101 naught101 commented Oct 25, 2017

I agree. I also think it would be worth clarifying that git pull is equivalent to git fetch && git merge origin/<upstream-branch>. That would demystify git pull a bit, as well as clarifying the separation between merging branches and interacting with an upstream repo.

@esmesh
Copy link

@esmesh esmesh commented Apr 10, 2019

8 - Collaborating mentions fetch, but only in the solution to the review changes challenge at the end.

As @naught101 mentions, pull should be clearly defined as a combination of fetch and merge.

@kekoziar
Copy link
Contributor

@kekoziar kekoziar commented Jul 4, 2019

I think git fetch is starting to go into intermediate territory, which is out of scope for a novice lesson. Maybe if this were a full-day lesson, but since it isn't we need to be careful that this novice lesson doesn't go out of scope.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
5 participants