Command Palette

Search for a command to run...

Hectal
Phase 3Intermediate4 of 9 in Git

Working with Remotes

A remote is just another copy of the repository with a name — clone, fetch, pull, and push are how you stay in sync with it.

Every collaboration workflow — a team sharing a repo, a fork-and-pull-request open-source contribution, a solo project backed up to GitHub — sits on top of exactly four operations: clone, fetch, pull, and push. This phase covers all four properly, plus the authentication (SSH keys and commit signing) that makes them actually work.

0/4 · 0%
4 topics ~56 min 6 code blocks & diagrams
Start with the first topic
1
3.1

Remotes, Clone, and Fetch vs Pull

A remote is a named reference to another copy of the repository somewhere else — clone downloads one for the first time, fetch checks for new history without touching your work, and pull is fetch immediately followed by a merge.

14 min 1 diagram 1 code practice

2
3.2

Push, Tracking Branches, and the Push/Pull Loop

git push sends your local commits to a remote, tracking branches remember which remote branch your local one corresponds to, and the push/pull loop is the entire daily rhythm of working with a shared repository.

14 min 1 code practice

3
3.3

Forks & Pull Requests

A fork is your own personal remote copy of someone else's repository — and a pull request is a formal request asking the original project to pull your changes back in, reviewed before anything merges.

14 min 1 diagram 1 code practice

4
3.4

SSH Keys, Git Authentication & Commit Signing

SSH keys let you push and pull without typing a password every time, and commit signing lets Git (and platforms like GitHub) cryptographically prove a commit genuinely came from you.

14 min 1 code practice