Merge independent contributions
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 cafe needs a clearer event title while another contribution clarifies what to bring.
A branch names a line of commits; a merge brings compatible histories together.
Merge independent contributions — guided practice
Use a branch to develop an isolated change and merge it.
Continue with main at two commits and untracked review.md. Keep review.md untouched. notice.txt has four lines.
1. Create a branch and edit
Run the switch command first. Then stop in the terminal: open notice.txt in your editor, change Repair Cafe to Neighborhood Repair Cafe, and save before continuing.
git switch -c title-updateYou should see: title-update is active and the saved file has the revised title.
The branch must be active before you make its intended edit.
2. Commit the branch edit
After saving the title change, inspect its diff, then stage and commit notice.txt.
git diff -- notice.txt git add notice.txt git commit -m "Name the neighborhood event"You should see: The branch contains a commit with the revised title.
The explicit edit-and-save pause prevents an empty commit attempt.
3. Return to main
Switch to main and read the first line.
git switch mainYou should see: It reads Repair Cafe again.
Switching changes the working files to that branch’s saved state.
4. Make separate work
Change Bring: one small item to Bring: one small unplugged item. Save, stage and commit.
git add notice.txt git commit -m "Clarify item preparation"You should see: Main now has the unplugged-item clarification.
Distinct contributions can be developed without overwriting each other.
5. Merge and inspect
Merge title-update into main and read the notice.
git merge --no-edit title-update git log --oneline --graph --allYou should see: Title and Bring changes both appear; Hours stays 10-12.
Compatible edits combine; inspect the result rather than assuming it is right.
What to finish
A merged title branch and an annotated history view.
Watch for this
Editing a file before switching without checking status can carry unintended work between branches.
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: Branch creation and resolving conflicting edits.
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.