Resolve a schedule conflict with a stated decision
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
Two cafe planners propose different opening hours. The approved decision is Hours: 11-13.
Conflict markers present alternatives; a person chooses the correct combined meaning.
Resolve a schedule conflict with a stated decision — guided practice
Resolve a deliberate same-line conflict using a supplied policy.
Continue on main after lesson 4. A disposable practice conflict is safe; do not run this in shared work. The approved policy for this exercise is open 11-13.
1. Create one proposal
Run the switch command. Then stop in the terminal: change Hours: 10-12 to Hours: 11-12 in your editor and save.
git switch -c hours-proposalYou should see: The proposal working file contains 11-12.
Switch before editing so the proposal begins from the intended branch.
2. Commit the opening proposal
After saving the 11-12 edit, stage and commit it.
git add notice.txt git commit -m "Propose later opening"You should see: hours-proposal has a saved opening change.
The edit must exist before staging can capture it.
3. Start the competing proposal
Switch to main with the command. Then stop in the terminal: change Hours: 10-12 to Hours: 10-13 in your editor and save.
git switch mainYou should see: The main working file contains 10-13.
The original main state supplies the competing same-line edit.
4. Commit the closing proposal
After saving the 10-13 edit, stage and commit it.
git add notice.txt git commit -m "Propose later closing"You should see: Main and hours-proposal now contain different committed changes to the same original line.
Both proposals need saved histories for this deliberate merge conflict.
5. Merge and decide
Run git merge hours-proposal. Open notice.txt and replace the entire conflict block, including all markers, with Hours: 11-13.
git merge hours-proposalYou should see: Exactly one Hours line remains and no marker lines remain.
Neither branch alone matches the approved combined decision.
6. Finish the merge
Stage notice.txt and commit the resolution. Read all four lines.
git add notice.txt git commit -m "Resolve hours to approved 11-13" git status --shortYou should see: The title, Bring and Access lines remain; Hours is 11-13.
Resolving the conflict should preserve unrelated correct content.
What to finish
A resolved merge and a one-sentence decision record in review.md.
Watch for this
Leaving <<<<<<<, ======= or >>>>>>> lines in the file after declaring a conflict resolved.
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: 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.