docs(course): drop the phase tags and the workflow built on them - #200
Conversation
The phase tags were never pushed. origin carries only v1.1.0-v1.5.0, so `git diff phase-2..phase-3` fails for everyone who clones this repo -- the course promised a history workflow no reader could run, in eleven places. Pushing them was the alternative, and it is worse. Every tag predates the loopback port binding and the dashboard uid fix: all eight publish ports on every interface (8 mappings at phase-0, rising to 18 at rfc-0002) and none pins a dashboard uid. Publishing eight trees that put Postgres on the wire, to an audience that will check them out and run them, is not worth a diff convenience. Better to not ship the footgun than to document it. The construction history is unaffected: every phase is a run of PRs on main, RFC-0001 Section 9 lists what each delivered, and the ADRs froze the decisions. The Tag column, the checkout instruction, the read-only-checkpoint paragraph, and the two "the rfc-000N tag will mark it" promises are gone. Tags deleted locally, recreatable from these commits if ever wanted: phase-0 8775267 Phase 0: repo restructure, CI, baseline hardening (#143) phase-1 99d458a Phase 1: three-layer monitoring, canary v1 (#159) phase-2 23170c3 Phase 2: contract-first gRPC + OpenTelemetry (#162) phase-3 a8ccbc0 Phase 3: Go analytics, pipeline-lag canary v2 (#167) phase-4 ec4810b Phase 4: load profile, Alertmanager, e2e gate (#172) phase-5 9cb1b1f Phase 5: historical seeder, workshop mode (#175) phase-6 393989a Phase 6: Kotlin reports, report load, canary v3 (#180) rfc-0002 e4bbafc RFC-0002: reports-ui Caddy static SPA (#182) All eight are ancestors of main, so the commits stay reachable regardless.
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
WalkthroughThe course documentation removes phase-tag browsing guidance, simplifies the course map, removes obsolete module tag references, and directs readers to ChangesCourse documentation guidance
Estimated code review effort: 1 (Trivial) | ~5 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
@coderabbitai review |
✅ Action performedReview finished.
|
|
@coderabbitai review |
✅ Action performedReview finished.
|
The phase tags were never pushed. origin carries only v1.1.0-v1.5.0, so
git diff phase-2..phase-3fails for everyone who clones this repo -- the course promised a history workflow no reader could run, in eleven places.Pushing them was the alternative, and it is worse. Every tag predates the loopback port binding and the dashboard uid fix: all eight publish ports on every interface (8 mappings at phase-0, rising to 18 at rfc-0002) and none pins a dashboard uid. Publishing eight trees that put Postgres on the wire, to an audience that will check them out and run them, is not worth a diff convenience. Better to not ship the footgun than to document it.
The construction history is unaffected: every phase is a run of PRs on main, RFC-0001 Section 9 lists what each delivered, and the ADRs froze the decisions. The Tag column, the checkout instruction, the read-only-checkpoint paragraph, and the two "the rfc-000N tag will mark it" promises are gone.
Tags deleted locally, recreatable from these commits if ever wanted:
phase-0 8775267 Phase 0: repo restructure, CI, baseline hardening (#143)
phase-1 99d458a Phase 1: three-layer monitoring, canary v1 (#159)
phase-2 23170c3 Phase 2: contract-first gRPC + OpenTelemetry (#162)
phase-3 a8ccbc0 Phase 3: Go analytics, pipeline-lag canary v2 (#167)
phase-4 ec4810b Phase 4: load profile, Alertmanager, e2e gate (#172)
phase-5 9cb1b1f Phase 5: historical seeder, workshop mode (#175)
phase-6 393989a Phase 6: Kotlin reports, report load, canary v3 (#180)
rfc-0002 e4bbafc RFC-0002: reports-ui Caddy static SPA (#182)
All eight are ancestors of main, so the commits stay reachable regardless.
Summary by CodeRabbit
mainbranch as the source of truth.