Estimated time — 20‑30 minutes
In real projects you’ll fix code on your fork, push, and open a pull request (PR).
This lab is a safe sandbox to practise that loop end‑to‑end.
By the end you will be able to:
- Fork a repository on GitHub.
- Clone your fork to your computer.
- Make a change (add a file).
- Commit and push that change back to your fork.
- Open a pull request so the original repo can review your work.
- Git installed and configured
- GitHub account added to our class org (check your email invite)
- Terminal (macOS/Linux) or Git Bash (Windows)
Screenshots count! Grab a screenshot at each 🚀 emoji and store them in a folder called
screenshots/.
- Visit the GitHub link given by your instructor.
- Click Fork → select your account.
- Confirm you’re now at
github.com/<you>/<repo‑name>.
git clone https://github.com/<your‑user>/<repo‑name>.git
cd <repo‑name># Bash
echo "My first lab ⭐" > hello-ironboard.txt
# PowerShell alternative:
# 'My first lab ⭐' > hello-ironboard.txtgit add hello-ironboard.txt
git commit -m "Add hello-ironboard.txt for Assignment 02"Check with git status.
git push -u origin main # use master if that’s the default branch- Go to your fork on GitHub.
- Click Compare & pull request.
- Title:
Complete Assignment 02 - Click Create pull request.
Create REFLECTION.md answering:
- Which step felt least clear?
- Why do we fork instead of pushing directly to the instructors’ repo?
git add REFLECTION.md
git commit -m "Add reflection"
git push-
hello-ironboard.txtpresent -
screenshots/with at least four images -
REFLECTION.mdadded - PR shows green checks
Paste your PR link in the LMS when done.
| Problem | Fix |
|---|---|
| Auth errors | Ensure you accepted the org invite; use HTTPS. |
| On wrong branch name | git branch -M main then push again. |
| Forgot a file | Add → commit → push; the PR updates automatically. |
Happy Git‑ing! 🚀