Deterministic main branch + fix two claims (#5,#13,#16) (#56)

Co-authored-by: claude <claude@jpaul.io>
Co-committed-by: claude <claude@jpaul.io>
This commit was merged in pull request #56.
This commit is contained in:
2026-06-22 14:58:51 -04:00
committed by Claude (agent)
parent e2a53c8259
commit 848ad14e3c
7 changed files with 33 additions and 12 deletions
@@ -233,8 +233,11 @@ from whichever forge's web form you happen to be filling in.
**You'll need:**
- Your `tasks-app` repo on a forge (Module 8), with issues enabled (they are by default on every
forge named in Module 8).
- Your `tasks-app` repo on a forge (Module 8), with its issue tracker enabled. Most forges turn
issues on by default, but not all of them do — consistent with the "the feature set varies" caveat
above. Bitbucket Cloud's tracker is off until you enable it, Azure DevOps uses Boards/Work Items
rather than an Issues tab, and SourceHut uses a separately provisioned `todo.sr.ht` tracker. If you
took the forge-agnostic path, confirm yours has issues available before Part C.
- The starter files in this module's `lab/` folder:
- `issue-template.md` — the well-formed-issue skeleton to copy for each issue.
- `example-issues.md` — three worked issues for `tasks-app`, as a reference/answer key.