forked from heavy-duty/ceremony
b2313beae8
Step 1 ruled what a rollup entry means and never said which entry to read. A job in a cancel-in-progress group displaces itself, so a head routinely carries a CANCELLED node beside the SUCCESS that replaced it, and read by class alone that head is not green while checks_state calls it SUCCESS. State the collapse ahead of the classes it feeds: newest entry by start time, and a CANCELLED entry is not the check's word while a non-cancelled sibling stands at the same head. All-cancelled and pending are untouched. Refs #276 |
||
|---|---|---|
| .. | ||
| 218.md | ||
| 230.md | ||
| 231.md | ||
| 232.md | ||
| 236.md | ||
| 237.md | ||
| 238.md | ||
| 241.md | ||
| 242.md | ||
| 247.md | ||
| 248.md | ||
| 251.md | ||
| 252.md | ||
| 254.md | ||
| 258.md | ||
| 260.md | ||
| 272.md | ||
| 276.md | ||
| 280.md | ||
| README.md | ||
| shape | ||
changelog.d/ — the next release's section, one fragment per issue
Machine-assembled by bin/changelog-assemble (#112): every PR that changes
behavior writes one file here — <issue>.md, the exact prose that will be
published, nothing else — and the release PR folds them all into the next
## X.Y.Z — DATE section of CHANGELOG.md, consuming them. Distinct
filenames never conflict, which is this directory's whole reason to exist.
This README is the marker that keeps the directory tracked when it holds no
fragments (#112 D1) — changelog-armed refuses a tree without it; do not
delete it. The shape sentinel beside it declares the set's shape —
grouped here, so every fragment carries ### headings (#182).