Remotes: Push, Pull, Fetch
Part of the Git course
Everything you have done so far lives only on your own machine. That is fine for practicing, but real projects need a shared copy other people, or other machines, can reach: a server holding the same repository so everyone's work ends up in one place. Git calls this a remote: another copy of your repository, usually hosted on a service like GitHub, that your local repository knows how to talk to.
This lesson needs a repository to push and a server to push it to. Press Play to create both in this lesson's folder (pressing it again starts over): hello-git with one commit, and server.git, an empty bare repository, one that holds only history and no working files, which is what a server keeps. It stands in for GitHub, so the lesson needs no account ...
Want to learn Git Remotes: Push, Pull, Fetch in a real environment?
Click below, get a fresh Linux box with Git ready to go, and work through Remotes: Push, Pull, Fetch hands-on with an AI tutor that knows your code.
Start this lessonRemotes: Push, Pull, FetchWhat you'll learn
- Git remote add
- Git push
- Git fetch
- Git pull
- Upstream tracking
Read this lesson in your language
All lessons in this course
13 lessons- 1Init and Your First Commit25 min
- 2Status, Diff, and Log25 min
- 3Branches and Merging30 min
- 4Resolving Merge Conflicts30 min
- 5Remotes: Push, Pull, Fetch30 min
- 6Stash and Cherry-pick25 min
- 7Rebasing30 min
- 8Interactive Rebase and Squashing30 min
- 9Tags and Releases20 min
- 10Branching Workflows20 min
- 11Recovering Lost Work25 min
- 12Hooks25 min
- 13Capstone: A Full Pull Request Flow40 min
