Hand off a reviewable repository
See this course’s project requirements
A local repository with a readable change history, two merged contributions, a resolved practice conflict, and an evidence-based review note.
Keep your working files in your own notebook or software. Save a private description, checklist, and work link in My Proof.
What to include
- Base and clarification commits.
- Review note grounded in an actual diff.
- Merged independent title contribution.
- Resolved hours conflict using the approved policy.
- Final files, history evidence and recovery note.
Review and revise
Use these criteria to check your work and choose what to improve.
- History records meaningful changes.
- Final notice matches all four required lines.
- Conflict resolution retains unrelated content.
- Review and recovery claims are accurate.
Want more background?
The idea in everyday life
The practice cafe project is ready for local review. No public push is required.
A handoff lets another person identify the current state, the reasons behind it, and the next safe step.
Hand off a reviewable repository — guided practice
Package a project with a truthful review and recovery plan.
Continue after lesson 5. Final notice: Neighborhood Repair Cafe; Hours: 11-13; Bring: one small unplugged item; Access: step-free entrance.
1. Complete the note
Extend review.md with final hours, the conflict decision, and a list of checks actually performed.
You should see: The note names the approved 11-13 choice and four final lines.
Handoffs explain judgment as well as files.
2. Record the handoff
Stage review.md and commit it.
git add review.md git commit -m "Document review and approved hours"You should see: The repository includes the notice and review note.
The handoff itself becomes part of project history.
3. Inspect a past version safely
Use git show HEAD:notice.txt and git log --oneline. Do not rewrite history.
git show HEAD:notice.txt git log --onelineYou should see: Current notice is displayed and earlier reasons are visible.
Read-only inspection avoids overwriting current work.
4. Write the recovery approach
Add to your external submission: for a shared mistaken commit, first inspect its diff and dependencies, then create a correcting commit or reviewed revert; do not force-push.
You should see: The plan preserves a review trail and acknowledges review before undo.
Recovery can affect later work, so it needs context.
What to finish
A local repository evidence package with the final notice, review.md, history evidence and recovery note.
Watch for this
Treating an untested recovery command as safe for a shared production repository.
How can I tell I understand it?
Complete the changed case, explain your result, and pass the three application checks.
Quick knowledge check
Answer all 3 questions. Get at least 2 right and the lesson completes automatically.
You’ll get an explanation for each answer. Signed in? Your results save to your account.
Pass the check. We’ll save the progress.
Answer all 3 questions above and get at least 2 right. You can review the explanations and try again.
Go to the knowledge checkOptional course overview video · same video as Lesson 1
Lecture 6: Version Control (git) (2020)
From Missing Semester. Watch here or open it on YouTube .
Optional course overview. Follow the written steps below at your own pace.Tools, templates, and lesson sources
Tools and templates
Tools open in a new tab so you can keep your place here.
Sources and further reading
Explore the references behind this lesson.
Source & access notes · checked 2026-09-12
Opened and inspected on 2026-09-12: Snapshots, staging, branch histories and collaboration.
Access: Free public web page; no paid enrollment required.
Reuse: CC BY-NC-SA; optional link only, no adapted prose or source exercises.
Source & access notes · checked 2026-09-12
Opened and inspected on 2026-09-12: Tracked, staged and modified states.
Access: Free public web page; no paid enrollment required.
Reuse: CC BY-NC-SA 3.0 book; link only.
Report a problem with this lesson
Tell us what went wrong. Please leave out personal information and private project contents.