# Knowledge Check: Remote Repositories

---

**1. What's the difference between `git fetch` and `git pull`?**

*Answer:* `git fetch` downloads the remote's new commits without touching your working files or
branches. `git pull` does that AND immediately merges them into your current branch — it's
fetch + merge combined.

---

**2. Why can `git pull` produce a merge conflict?**

*Answer:* Because it performs a real merge under the hood — if your local branch and the
remote's branch both changed the same lines differently, the same conflict situation from
Module 4 can occur.

---

**3. Is `origin` a required, special name Git enforces?**

*Answer:* No — it's just the conventional default name Git assigns to the remote you cloned
from. You could name a remote something else; `origin` is a widely recognized convention, not a
technical requirement.

---

**4. Does this course require a GitHub or Gitea account to learn remotes?**

*Answer:* No — this course uses a disposable local bare repository to safely simulate a real
remote, teaching the same concepts (clone/fetch/pull/push/origin) without any account or network
access.

## Instructor Notes

**Facilitation:** Question 2 is worth emphasizing — many students assume `pull` is risk-free
until they hit their first real pull-conflict.

**Approximate timing:** 5 minutes.