Skip to main content

Remotes for Git and GitHubs

Remotes are copies of a repository hosted elsewhere, usually on GitHub, that you synchronise with using git push, git fetch and git pull. Pull requests are the GitHub mechanism for proposing changes from a branch or fork, discussing them, and merging after review.

Stage: GitHub Collaboration · Part of the Git and GitHub roadmap · Last reviewed 19 November 2026

What to learn in Remotes

Remotes interview questions

What is the difference between git fetch and git pull?

Fetch downloads new commits and updates remote-tracking branches but leaves your working branch alone. Pull is fetch followed by a merge, or a rebase if configured, into your current branch. Fetching first lets you inspect changes before combining them.

What is a fork versus a clone?

A clone copies a repository to your machine. A fork is a copy of someone else's repository on your own GitHub account, letting you push changes you could not make to the original and propose them back through a pull request.

Where Remotes fits in the Git and GitHub roadmap

Remotes belongs to the GitHub Collaboration stage (beginner level), which takes about 9 hours. Work with a team.

Back to the full Git and GitHub roadmap