Stop presenting git rebase / git pull --rebase as a casual fix before any module introduces it
#34
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
Rebase is in no module's introduced-concepts list, yet it is used as a fix/choice: M8 offers
git pull --rebase origin mainas a first-push reconcile, M11 references rebasing as a merge strategy and a remedy for a movedmain, and M26 Problem 4 says "rebase/merge the others on top." Learners are told to run/choose rebase with no model of what it does.Evidence
modules/08-remotes-and-hosting/README.mdfailure mode #2 (~line 115): "reconcile once withgit pull --rebase origin mainand then push."modules/26-orchestrating-multiple-agents/README.mdProblem 4 (~line 193): "then rebase/merge the others on top."modules/11-.../README.md(~lines 107, 402) mentions rebase. Rebase is never taught in any module.Why it matters
Violates "never reference a tool before its introducing module," and the M8 line actually instructs a first-remote user to RUN an unexplained rebase that can drop them into a README conflict.
Proposed change
--rebaseas advanced and cross-reference Module 11. Do NOT replace--rebasewith plaingit pullhere — that fails with "refusing to merge unrelated histories" against an auto-README remote, so a footnote (not removal) is correct.git merge).Acceptance criteria
Affected files
modules/08-remotes-and-hosting/README.md,modules/26-orchestrating-multiple-agents/README.md,modules/11-collaboration-humans-and-agents/README.mdReferences
Source finding F14 (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.