ced4568andClaude Sonnet 5
e68b6f445a
Adds all 6 ROOT 03 modules (why version control exists, the Git mental model, everyday Git, branching & merging, remote repositories, engineering Git workflow) — 31 activities. Uses only real LOCAL Git repositories throughout — no Gitea account, no network access, and no RootNode-canonical-repo credential is ever needed or exposed in a student Lab (docs/ROOT_FOUNDATIONS_LAB_STRATEGY.md §4). Modules 1, 2, and 6 are conceptual bookends with no lab, matching the flexible readiness standard already used in ROOT 01/02. Adds 3 new hands-on Git scenarios plus 2 MCQs: git-everyday-basics (init/add/commit, validated by inspecting real `git log`/`git show` state, not just command output strings — Step 6's explicit requirement), git-branching-and-merge (a REAL merge conflict caused on purpose by two branches editing the same line, resolved by the student, validated by confirming the conflict markers are gone and a real two-parent merge commit exists), and git-remote-clone-push (a real local bare repository standing in for a remote — clone/commit/push validated by inspecting the REMOTE side directly, not just the student's own clone). All tested end-to-end via the real scenario-validation API, including negative tests. Wires rootnode-git-fundamentals-assessment (2 required + 3 random-draw scenarios) using the existing Phase 3B assessment engine. Co-Authored-By: Claude Sonnet 5 <[email protected]>
1.1 KiB
Knowledge Check: Why Version Control Exists
1. Name three real properties version control gives you that copying files as backups doesn't.
Answer: Any three of: structured history of every change, reproducibility of exact past states, real collaboration between multiple people, a single agreed-upon source of truth, confident rollback to a known-good state.
2. Why does final_v2_ACTUALLY_FINAL.txt fail as a version-control strategy?
Answer: It has no record of what changed or why between versions, doesn't scale past a handful of files, and provides no way to merge two people's simultaneous changes.
3. What does "source of truth" mean in the context of version control?
Answer: One authoritative, agreed-upon history of a project that everyone treats as correct — as opposed to ambiguity over which copy or filename is the "real" current version.
Instructor Notes
Facilitation: Keep this brief — it's checking motivation/vocabulary before the hands-on modules begin, not testing depth yet.
Approximate timing: 4 minutes.