MODULE 03 · 6 MIN READ
The exercise: introduce yourself, the Git way
Teams don't push straight to main. The professional flow uses everything from all three days: branch → commit → push the branch → open a pull request → someone reviews → merge.
A pull request (PR) is just a webpage that says "here are my commits — please pull them into main," with a discussion thread attached.
Your mission
Exactly as in the live session: create a branch named after your employee ID, write a small about-me file at about/<your-id>.md (2–3 lines — team, what you're learning, a fun fact), push the branch, and open a PR.
Everyone owns a different file, so nobody can conflict with anybody — and the branch list becomes the class roster.
$ git switch -c EMP1234
Switched to a new branch 'EMP1234'
$ echo "Hi, I'm Ada — I love commit graphs" >> about/EMP1234.md
✏️ wrote "Hi, I'm Ada — I love commit graphs" into about/EMP1234.md
$ git commit -am "Add about file for EMP1234"
$ git push
Pushed branch 'EMP1234' → origin ☁️
remote: Create a pull request for 'EMP1234' on GitHub
💻 YOUR LAPTOP
☁️ GITHUB · origin/main
🏆 THE TEAM — about/ on main
a tiny simulated laptop, wired up to a fake GitHub. clone to begin.
// try: git clone ... → git switch -c EMP1234 → echo "your intro" >> about/EMP1234.md → git commit -am "Add about file for EMP1234" → git push — then click the buttons in the panel above