Skip to content

ci: fold the four daily patrols into one fleet-patrols.yml workflow (1 of 3) #26512

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
os-zhuang merged 1 commit into from
Oct 27, 2026
+1,499 −1,406
Merged

ci: fold the four daily patrols into one fleet-patrols.yml workflow (1 of 3) #26512

Show file tree
Hide file tree
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
429 changes: 0 additions & 429 deletions .github/workflows/board-snapshot.yml
View file
Open in desktop

This file was deleted.

1,427 changes: 1,427 additions & 0 deletions .github/workflows/fleet-patrols.yml
View file
Open in desktop

Large diffs are not rendered by default.

427 changes: 0 additions & 427 deletions .github/workflows/platform-checklist-watchdog.yml
View file
Open in desktop

This file was deleted.

308 changes: 0 additions & 308 deletions .github/workflows/release-coverage-patrol.yml
View file
Open in desktop

This file was deleted.

207 changes: 0 additions & 207 deletions .github/workflows/required-set-patrol.yml
View file
Open in desktop

This file was deleted.

4 changes: 2 additions & 2 deletions docs/qa/platform-checklist/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -211,7 +211,7 @@ Why this shape:
census and not a verdict). Adding anchors never reds; ⛔ lowering a floor is
MAINTAINER-ONLY. ⚠️ Note what a red here reaches: `check:platform-checklist` is not
CI-wired (see "Operating cadence"), so it reaches whoever runs the gate — **not every
PR** — plus the daily `platform-checklist-watchdog` workflow, which files or refreshes
PR** — plus the daily `platform-checklist-watchdog` job of `fleet-patrols.yml`, which files or refreshes
one issue when the gate is red.
- **`why` is the debt marker.** A recipe exists because stock fixtures cannot demonstrate
something — the same discipline as a coverage waiver. Landing the fixture in the
Expand Down Expand Up @@ -433,7 +433,7 @@ checklist drift. It runs on a **manual / periodic cadence** instead. Run
- **alongside a `checklist-author`** (find gaps) **or `checklist-test`** (execute items).

A red gate does have a reporting channel, and it is not this cadence:
[`.github/workflows/platform-checklist-watchdog.yml`](../../../.github/workflows/platform-checklist-watchdog.yml)
the `platform-checklist-watchdog` job of [`.github/workflows/fleet-patrols.yml`](../../../.github/workflows/fleet-patrols.yml)
runs `pnpm check:platform-checklist` on `main` daily and files or refreshes one issue when
it is red (⛔ and does nothing when it is green). That closes the visibility half only —
the cadence above is still how the gate gets run *before* a red can matter.
Expand Down
2 changes: 1 addition & 1 deletion docs/qa/platform-checklist/RUNNER.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,7 +14,7 @@ contract.
**Who sees a red gate.** `pnpm check:platform-checklist` is not wired into per-PR CI (a
standing maintainer decision — see the README's "Operating cadence"), so the channel that
sees its red is
[`.github/workflows/platform-checklist-watchdog.yml`](../../../.github/workflows/platform-checklist-watchdog.yml):
the `platform-checklist-watchdog` job of [`.github/workflows/fleet-patrols.yml`](../../../.github/workflows/fleet-patrols.yml):
it runs the gate on `main` daily, files or refreshes exactly one issue when the gate is red,
and does nothing at all when it is green.

Expand Down
Loading
Loading