feat(recipe-report): TESTS rename + live binary STATUS column
Rename the table's Status column -> TESTS (the CI/test verdict, unchanged content). Add a new STATUS column showing the PR's LIVE state, fetched client-side: 'open' vs a ✓ for any not-open state (merged or closed). The cell is a JS hook (data-repo/data-pr) derived from existing recipe+pr fields; an inline, dependency-free, CSP-safe script GETs the same-origin /pr/<recipe>/<n> proxy (cc-ci nix/modules/reports.nix) on load and every 30s, and degrades to a muted '?' if the proxy/repo is unreachable. Blank cell when a row has no PR. Doc + SKILL updated. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This commit is contained in:
co-authored by
Claude Opus 4.8
parent
eb1439324e
commit
f687174b53
@@ -56,6 +56,11 @@ Helper: `python3 /srv/cc-ci/cc-ci-plan/recipe-report.py {survey|render|publish}`
|
||||
`status` GREEN/FAILED/STALE/SKIPPED/UPTODATE, **`cve`** (integer count of CVEs this PR fixes; `0`
|
||||
or omit for none), `ci` as a level/result number+info string e.g. `build 154 ✓` or `RED 200 ·
|
||||
install` with `ci_url`, `pr`/`pr_url`, `notes`. **CI = link + number/info only; no images.**
|
||||
- The table renders **two** status columns: **TESTS** (the `status` field — the CI/test verdict)
|
||||
and **STATUS** (the PR's LIVE state, fetched client-side). You only supply `status`; the live
|
||||
STATUS column is derived automatically from `recipe` + `pr` and needs no spec field — it shows
|
||||
`open` vs a ✓ (any not-open state), refreshing ~30s via the same-origin `/pr/<recipe>/<n>` proxy
|
||||
(cc-ci `nix/modules/reports.nix`); it degrades to a muted "?" if the proxy/repo is unreachable.
|
||||
- `addendum[]` — list of bullet strings (may be empty),
|
||||
- `security[]` — critical-CVE bulletin entries (may be empty),
|
||||
- `changes[]` — `{recipe, body, links[]}`, one per recipe that has a PR.
|
||||
|
||||
Reference in New Issue
Block a user