Create a local project history
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
A team is preparing a fictional repair-cafe notice. Practice entirely inside a new folder named git-lab.
A commit is a saved project state with a reason; a working file can change before the next snapshot.
Create a local project history — guided practice
Create a repository and identify its first snapshot.
Install free Git first. Create an empty git-lab folder and open a terminal there. Create notice.txt containing exactly: Repair Cafe Hours: 10-12 Bring: one item . Use the supplied file; no real contact details.
1. Initialize
Run git init, then set this repository’s practice identity.
git init -b main git config user.name "Practice Learner" git config user.email "learner@example.invalid"You should see: Git creates a repository; configuration affects this folder only.
Local identity avoids changing other projects.
2. Inspect
Run git status --short.
git status --shortYou should see: ?? notice.txt appears.
Untracked means the file is not yet in a snapshot.
3. Save
Stage notice.txt, then commit it with the supplied message.
git add notice.txt git commit -m "Add repair cafe notice"You should see: One commit is created.
Only explicitly staged content is recorded.
4. Verify
Run the count and status commands.
git rev-list --count HEAD git status --shortYou should see: Commit count is 1; short status prints no file changes.
History and working state answer different questions.
What to finish
A repository with one base commit and a saved count/status note.
Watch for this
Running git init in an existing personal project makes the exercise state unclear.
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
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.
Source & access notes · checked 2026-09-12
Metadata retrieved and inspected on 2026-09-12: exact title and channel confirmed through YouTube oEmbed. Playback and full video content were not tested. Optional overview; the written lesson and supplied practice stand alone.
Access: Free public web page; no paid enrollment required.
Reuse: Link or provider embed only; do not copy video, audio or transcript.
Report a problem with this lesson
Tell us what went wrong. Please leave out personal information and private project contents.