Everything you need before the bell rings
Learning Objectives
Students will be able to…
- ✓Explain a repository and commits.
- ✓Use branches safely.
- ✓Keep a team in sync.
- ✓Plan a Git workflow.
How do teams track changes and work on code together without chaos?
The Git Explorer
Project this and tap each. Have students explore the core ideas of version control.
55 minutes, five moves
Tap any phase to open the teacher moves and student actions.
Hook — Who Changed What?
How does a team avoid overwriting each other’s code?
👩🏫 Teacher Moves
- Show a messy shared file.
- Ask how pros manage it.
- Set the goal.
🎒 Student Actions
- Think.
- Guess.
- Get ready.
Use — Version Control
Students use the idea.
👩🏫 Teacher Moves
- Send students to the Git Explorer.
- Tap each concept.
- Note commit, branch, push/pull.
🎒 Student Actions
- Tap each.
- Say.
- Note it.
Modify — Branch & Merge
Students modify.
👩🏫 Teacher Moves
- Create a branch for a feature.
- Make a commit on it.
- Merge it back to main.
🎒 Student Actions
- Branch.
- Commit.
- Merge.
Create — Plan a Workflow
Students create.
👩🏫 Teacher Moves
- Write a 4-step team workflow.
- Decide who branches when.
- Add a commit-message rule.
🎒 Student Actions
- Write.
- Decide.
- Add.
Reflect — Reflect
Students close.
👩🏫 Teacher Moves
- Say what a commit is.
- Say why branches help.
- Complete the exit ticket.
🎒 Student Actions
- Say it.
- Say.
- Complete the exit ticket.
Built to the standards you report on
Aligned to the CSTA K-12 Computer Science Standards and the ISTE Standards for Students.
Design and develop artifacts working collaboratively.
Document a program to make it easier to test and debug.
Decompose work into parts for a team.
Use collaborative tools to work with others.
One lesson, every learner
Multilingual Learners
- Use a “track changes” analogy.
- Frame: “save, branch, merge, sync.”
- Label a Git diagram.
Support & Access
- Start with commit & repo.
- One concept at a time.
- Use pictures.
Stretch & Extend
- Resolve a merge conflict (in theory).
- Write good commit messages.
- Try a pull request.
What to gather
- 📽️Screen / board
- 🌿Git concept cards
- 💻The Git Explorer
- 🐙GitHub (optional)
- 📓Notebooks
- 🎫Exit-ticket slips
Key terms — hover for a quick definition
Exit Ticket
Preview the three formative checks. Tap “Sample answer” to see what mastery looks like — hide them before you print for students.
Reflect: version control.
Have students write a 4-step Git workflow for a team project. A printable version-control worksheet is in the Computer Science library.
Study the key terms
Tap a card to flip it, then rate whether you knew it. Built from this lesson’s vocabulary.
Nice work!
Check your understanding
A quick self-check with instant feedback, drawn from this lesson’s key terms.
Nice work!
Printable worksheet
A print-and-go review sheet with a built-in answer key. Tap “Show answer key” to reveal answers, or print the clean version for students.
Part A · Write the word that matches each meaning
- upload commits to a shared server
- a project and its full history (repo)
- combine a branch into the main code
- download others’ changes
- two changes to the same line
- tracking changes to code over time
- a saved snapshot with a message
- a separate line of work
Part B · Show what you learned
- What is a commit?
- Why use branches?
- What do push and pull do?
Part B: 1) A saved snapshot of your changes with a message. 2) To work on a feature without touching the main code. 3) Push uploads your commits; pull downloads teammates’ changes.