Home›Lesson Plans›Computer Science›Collaboration · Grade 10

Version Control with Git

Tenth graders learn how professional teams track their code with Git. A repository keeps the full history; commits are snapshots; branches let you work safely in parallel; and push/pull keeps a team in sync. They explore each idea, then plan a simple Git workflow.

Grade 10Version Control with Git55 minutes1 class periodCSTA / ISTEExplicit teaching4 StandardsCSTA
Start the Lesson
Assign or share this lesson
Share to Google Classroom Share to Microsoft Teams

Copy link works with Canvas, Schoology, Moodle and any other LMS — paste it in as a resource or assignment.

Lesson at a Glance

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.
Essential Question

How do teams track changes and work on code together without chaos?

0
Lesson Phases
0
Vocabulary Terms
0
Standards Aligned
0
Interactive Task
Explore · Interactive

The Git Explorer

Project this and tap each. Have students explore the core ideas of version control.

🌿 Explore version control with Git — tap eachTry it

The Lesson · Use → Modify → Create (a coding progression with Unplugged practice)

55 minutes, five moves

Tap any phase to open the teacher moves and student actions.

1

Hook — Who Changed What?

6 min

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.
2

Use — Version Control

13 min

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.
3

Modify — Branch & Merge

14 min

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.
4

Create — Plan a Workflow

15 min

Students create.

👩‍🏫 Teacher Moves

  • Write a 4-step team workflow.
  • Decide who branches when.
  • Add a commit-message rule.

🎒 Student Actions

  • Write.
  • Decide.
  • Add.
5

Reflect — Reflect

7 min

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.
Standards Alignment

Built to the standards you report on

Aligned to the CSTA K-12 Computer Science Standards and the ISTE Standards for Students.

CSTA
3A-AP-22

Design and develop artifacts working collaboratively.

CSTA
3A-AP-23

Document a program to make it easier to test and debug.

CSTA
3A-AP-17

Decompose work into parts for a team.

ISTE
7 Global Collaborator

Use collaborative tools to work with others.

Differentiation

One lesson, every learner

Multilingual Learners

ELL / EMERGING READERS
  • Use a “track changes” analogy.
  • Frame: “save, branch, merge, sync.”
  • Label a Git diagram.

Support & Access

IEP / 504
  • Start with commit & repo.
  • One concept at a time.
  • Use pictures.

Stretch & Extend

GIFTED / EARLY FINISHERS
  • Resolve a merge conflict (in theory).
  • Write good commit messages.
  • Try a pull request.
Materials

What to gather

  • 📽️Screen / board
  • 🌿Git concept cards
  • 💻The Git Explorer
  • 🐙GitHub (optional)
  • 📓Notebooks
  • 🎫Exit-ticket slips
Vocabulary

Key terms — hover for a quick definition

version controltracking changes to code over timerepositorya project and its full history (repo)commita saved snapshot with a messagebrancha separate line of workmergecombine a branch into the main codepushupload commits to a shared serverpulldownload others’ changesconflicttwo changes to the same line
Evaluate

Exit Ticket

Preview the three formative checks. Tap “Sample answer” to see what mastery looks like — hide them before you print for students.

QUESTION 1
What is a commit?
A saved snapshot of your changes with a message.
QUESTION 2
Why use branches?
To work on a feature without touching the main code.
QUESTION 3
What do push and pull do?
Push uploads your commits; pull downloads teammates’ changes.

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 · Flashcards

Study the key terms

Tap a card to flip it, then rate whether you knew it. Built from this lesson’s vocabulary.

🃏 CS Version Control with Git (Grade 10)Flip
Card 1
Term
Tap to flip →
Meaning
0

Nice work!

Practice · Quiz

Check your understanding

A quick self-check with instant feedback, drawn from this lesson’s key terms.

📝 CS Version Control with Git (Grade 10)Quiz
Score: 0
1 / 6
Question 1
0%

Nice work!

Practice · Worksheet

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.

🖨️ CS Version Control with Git (Grade 10)Print
Name: ________________________
Date: ____________

Part A · Write the word that matches each meaning

Word bank: branch, commit, conflict, merge, pull, push, repository, version control
  1. upload commits to a shared server
  2. a project and its full history (repo)
  3. combine a branch into the main code
  4. download others’ changes
  5. two changes to the same line
  6. tracking changes to code over time
  7. a saved snapshot with a message
  8. a separate line of work

Part B · Show what you learned

  1. What is a commit?
  2. Why use branches?
  3. What do push and pull do?
Answer key — Part A: 1) push · 2) repository · 3) merge · 4) pull · 5) conflict · 6) version control · 7) commit · 8) branch
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.