Add Module 3 to Module 6's prerequisites and back-reference the branch material it first taught #35
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Problem
Module 3 introduces
git branch,merge,switch -c, fast-forward, the switch-vs-checkout note, and usesgit branch -d, explicitly forward-pointing to Module 6 for real code work. But Module 6 lists only Modules 2/4/5 as prerequisites, never references Module 3, and re-derives "what a branch is," the switch-vs-checkout naming note, and fast-forward as brand new — breaking chain accounting in a course that markets its dependency chain.Evidence
modules/06-branches-sandboxes-for-experiments/README.mdPrerequisites list only Modules 2/4/5; concept re-derivation (~lines 44-57, 67-70, 131-143).modules/03-version-control-for-words/README.mdintroduces branch/merge/switch -c/fast-forward and usesgit branch -d(~lines 130, 297), forward-pointing to Module 6.Why it matters
M3 explicitly forward-points to M6, but M6 never reciprocates — a one-directional link in a course whose dependency chain is load-bearing.
Proposed change
restore) — cross-link to M3 rather than trimming it to a bare back-reference.Note: drop the original finding's "reconcile the command map for
git branch -d" item — no such command/verb map exists in the repo.Acceptance criteria
Affected files
modules/06-branches-sandboxes-for-experiments/README.mdReferences
Source finding F17 (realVotes 3/3).
Filed from an adversarial multi-agent course review (217 raw findings → 54 adversarially-verified survivors). Scoped for manual review; intentionally not auto-assigned to an agent.