justin/ai-workflow-course
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs(m1 starter): keep the tasks-app scope note honest across the course
CI / check (pull_request) Successful in 6s
Details

Browse Source 
The starter README said tasks-app is the running example for M1 and M2 only.
In reality it's used from M1 through the capstone: agent-driven edits in M4,
worktrees drive it in M7, the review lab pastes a patch onto it in M10, and
so on. Tighten the note to reflect actual scope.

Ports back the same change already merged on the GitHub mirror
(recklessop/ai-workflow-course#2) so it survives the next Gitea -> GitHub sync
instead of getting overwritten.
This commit is contained in:
Claude (agent)
2026-07-02 15:57:55 -04:00
parent f61c46fe19
commit bcd20283f3
1 changed files with 1 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
modules/01-the-copy-paste-problem/lab/starter/README.md
+1 -2
View File
@@ -4,8 +4,7 @@ A deliberately tiny command-line task tracker. It exists to be *changed by an AI
enough to read in a minute but real enough to have more than one file, which is exactly where the
copy-paste workflow starts to hurt.
This is the running example for **Module 1** (where you feel the copy-paste problem) and **Module 2**
(where you put it under version control).
This is the running example throughout the course: pain in Module 1, safety net in Module 2, docs in Module 3, agent-driven edits in Module 4, and it keeps showing up all the way to the capstone.
## Files