The advisory */15 cron fired a full-board sweep four times an hour at GitHub's 1-minute billing floor; events carry real state changes in seconds, so the cron only backstops a forgotten handoff. Relax it to hourly and narrow the issues: trigger to [opened, closed] — the two actions with promptness-critical reconcile behavior — dropping the labeled/unlabeled churn source. Per-trigger why-comments added. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| 167.md | ||
| 173.md | ||
| 175.md | ||
| 178.md | ||
| 180.md | ||
| 182.md | ||
| 184.md | ||
| 187.md | ||
| 189.md | ||
| 192.md | ||
| 193.md | ||
| 199.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).