docs: sort Prerequisites lists numerically ascending (#100)
CI / check (pull_request) Successful in 6s
CI / check (pull_request) Successful in 6s
Reorder the `## Prerequisites` bullets in 9 modules so prior modules are listed lowest number first instead of by pedagogical importance or at random. A trailing "Helpful but not required" group stays last and is sorted within itself; multi-module bullets sort by their lowest number. Intro/closing paragraphs are left in place. Prose is unchanged; only bullet order moves. Modules touched: 7, 9, 14, 15, 22, 24, 25, 26, 27. The other 18 modules were already ascending (or have one/zero prereqs) and are untouched. Module 19's "Helpful but not required: Module 16" correctly trails its ascending 8/14/18 main list, so it stays as is. Closes #100 Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01CamgR4HaVpfaqUViuHUcWw
This commit is contained in:
@@ -8,15 +8,15 @@
|
||||
|
||||
## Prerequisites
|
||||
|
||||
- **Module 6: Branches.** You can create a branch, switch to it, merge it back, and resolve a
|
||||
conflict. A worktree is the physical counterpart to the logical isolation a branch already gives
|
||||
you, so this module makes no sense without it.
|
||||
- **Module 4: Getting the AI out of the browser.** The agents in this module edit real files in a
|
||||
folder. You'll point an editor-integrated AI session at each worktree directory.
|
||||
- **Module 1: the `tasks-app`.** The running example continues here.
|
||||
- **Module 2: Version control.** The `tasks-app` is already a Git repo with commits, and you read
|
||||
a project's state from `git status` / `git diff` / `git log`. Each worktree has its own answer to
|
||||
those, which is the whole point.
|
||||
- **Module 1: the `tasks-app`.** The running example continues here.
|
||||
- **Module 4: Getting the AI out of the browser.** The agents in this module edit real files in a
|
||||
folder. You'll point an editor-integrated AI session at each worktree directory.
|
||||
- **Module 6: Branches.** You can create a branch, switch to it, merge it back, and resolve a
|
||||
conflict. A worktree is the physical counterpart to the logical isolation a branch already gives
|
||||
you, so this module makes no sense without it.
|
||||
|
||||
If you parachuted in: you minimally need a Git repo with at least one commit and a working
|
||||
understanding of branches.
|
||||
|
||||
Reference in New Issue
Block a user