Outcomes
What students should leave with
- Create repositories, commits, and branches with meaningful history.
- Use pull requests or review checkpoints to protect shared work.
- Document work clearly enough for instructors and teammates to follow.
Reference map
Core topics to cover
Repositories
Commits
Branches
Pull requests
Merge strategy
Release notes
Project hygiene
Module sequence
ICCT lesson flow
Module 1
Core repo habits
Lessons: 2
Learn how to save work in a way that others can trust.
Repositories, staging, and commits
clean commit messages and useful snapshots
History reading and rollback thinking
understanding the story of a project
Checkpoint lab
Initialize a course project repo and capture meaningful milestone commits for the first build steps.
Module 2
Collaboration flow
Lessons: 2
Move from solo work to shared delivery.
Branches and focused changes
small units of work and naming discipline
Review and merge routines
handoff notes, review requests, and safe integration
Checkpoint lab
Simulate a student team workflow with one feature branch, one review pass, and one merge.
Module 3
Project reliability
Lessons: 2
Support instructors and future teammates with better documentation.
README expectations and setup notes
making projects runnable by others
Release thinking and change logs
communicating progress and shipped work
Checkpoint lab
Prepare a weekly release summary that explains what changed, what is still pending, and how to test it.
Capstone prompts
Projects students can actually ship
Team Capstone Repo
Run a shared project with branches, review checkpoints, and documented milestones.
Weekly Change Log
Summarize shipped work, open questions, and testing notes in a repeatable format.