check-issue-refs: catch ambiguous owner#N cross-repo refs in markdown too
This commit is contained in:
parent
9d02d81144
commit
786ab304d6
9 changed files with 64 additions and 39 deletions
|
|
@ -85,7 +85,7 @@ structurally rather than for one specific trigger. Two columns:
|
|||
`agent_links()` in hive-agent is the single source of truth for
|
||||
both. No separate overflow (`⋯`) menu exists any more — it used
|
||||
to hold exactly this dashboard link plus a rebuild-container action
|
||||
(mara, hyperhive#3704: "remove rebuild button, move link to
|
||||
(mara, #3704: "remove rebuild button, move link to
|
||||
dashboards into links menu") — rebuild had no real discoverability
|
||||
need of its own (the dashboard's own R3BU1LD button already covers
|
||||
it) so it's gone outright, and the dashboard link moved here,
|
||||
|
|
|
|||
|
|
@ -236,7 +236,7 @@ than reconstructing chrome hive-c0re no longer sends. Settled entries
|
|||
render their **full step tree**, not just a bare summary — the wire
|
||||
doesn't filter `Done` nodes out.
|
||||
|
||||
**State filter (hyperhive#2606).** A row of per-state checkboxes above
|
||||
**State filter (#2606).** A row of per-state checkboxes above
|
||||
the tree — one per lifecycle state, matching the row glyphs — lets the
|
||||
operator narrow which root groups render; unchecking a state re-fetches
|
||||
`GET /api/jobq/graph?states=<checked, comma-joined>` rather than
|
||||
|
|
@ -811,7 +811,7 @@ below).
|
|||
|
||||
### Status badges
|
||||
|
||||
**Which single badge (hyperhive#3139):** `ContainerView.failed`
|
||||
**Which single badge (#3139):** `ContainerView.failed`
|
||||
(systemd `ActiveState=failed` — the unit exhausted its bounded
|
||||
restarts and gave up on its own) draws a red `✖ gave up` badge;
|
||||
otherwise a plain muted `■ not running` — a container an operator
|
||||
|
|
|
|||
|
|
@ -244,7 +244,7 @@ render, `restoreOpenDetails()` re-applies after. Long-content
|
|||
drill-ins (file previews, diffs, journald logs) now open in the
|
||||
**side panel** (see below) rather than expanding inline. The
|
||||
dashboard's own answered-questions history list was the only
|
||||
`<details data-restore-key>` consumer and is gone (hyperhive#3721)
|
||||
`<details data-restore-key>` consumer and is gone (#3721)
|
||||
— `snapshotOpenDetails()` / `restoreOpenDetails()` currently have
|
||||
nothing to restore, kept in place for the next collapsible section
|
||||
that needs it rather than ripped out along with their one caller.
|
||||
|
|
|
|||
Loading…
Reference in a new issue