Skip to content

docs(launch): fix stale refresh-metrics.yml row in readiness gate #579

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
castrojo merged 1 commit into from
Sep 24, 2026
Merged

docs(launch): fix stale refresh-metrics.yml row in readiness gate #579

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 9 additions & 5 deletions LAUNCH.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -74,11 +74,15 @@ shipping stale content on day one — the exact failure this automation exists t
prevent. Before the W-0 launch date, all scheduled content-refresh workflows
must be green for **2 consecutive scheduled runs**:

| Pipeline | Schedule | Tracking |
| ----------------------------------------------------------- | -------- | ------------ |
| Import reference architectures (`import-architectures.yml`) | daily | #121 |
| Refresh community profiles (`refresh-community-people.yml`) | weekly | #122 |
| Metrics refresh (`refresh-metrics.yml`, not yet merged) | daily | #74, PR #125 |
| Pipeline | Schedule | Tracking |
| -------------------------------------------------------------------------------------------- | -------- | -------- |
| Import reference architectures (`import-architectures.yml`) | daily | #121 |
| Refresh community profiles (`refresh-community-people.yml`) | weekly | #122 |
| Metrics refresh (`collect:metrics` + `validate:metrics` steps of `import-architectures.yml`) | daily | #121 |

A dedicated `refresh-metrics.yml` workflow was proposed in PR #125 and declined
(#74); metrics refresh instead runs as steps inside `import-architectures.yml`,
so it shares that workflow's tracking issue and readiness signal.

If any pipeline is still red at W-1, treat it the same as any other Phase 1
blocker under "Full content freeze rehearsal" (W-4): either land the fix or
Expand Down