forked from heavy-duty/ceremony
8cf3c335df
The trigger comments, CONSUMERS stub, changelog, and reusable labels.yml comment said "events carry every real state change in seconds; the cron only backstops a forgotten handoff." That is backwards: no subscribed event wakes this sweep for a review verdict landing (no pull_request_review trigger), blocker:ci-red set/cleared, blocker:conflict when another PR merges, or the time-based stale/48h-reclaim. The hourly cron is the sole discovery path for those four classes, not a forgotten-handoff net — so the comments now name them and warn against deleting the cron (AC5). codex-2 / kimi-2 (both blocking, round 2 @0a812c4b).
17 lines
1 KiB
Markdown
17 lines
1 KiB
Markdown
### Changed
|
||
|
||
- `labels` — the reconcile cron relaxes from `*/15` to hourly (#199), cutting a
|
||
private consumer's schedule-triggered full-board sweeps ~4× at GitHub's
|
||
1-minute billing floor.
|
||
- `labels` — the hourly cron is the sweep's only wake for transitions no
|
||
subscribed event carries — a verdict landing, blocker:ci-red, a
|
||
blocker:conflict when another PR merges, the time-based stale/reclaim — so it
|
||
bounds their latency to ≤1h, delaying no event-carried transition (#199).
|
||
- `labels` — the caller's `issues:` trigger narrows to
|
||
`[opened, closed, edited, reopened]` (#199), the actions that carry a
|
||
queue-state change the cron cannot wait a cadence for. The churn/validation
|
||
actions — labeled/unlabeled/assigned/unassigned — come off; the PR handoff
|
||
wake is unaffected.
|
||
- `labels` — each caller trigger now carries a comment saying why it is
|
||
subscribed, and reconcile keeps `cancel-in-progress: false` (#199) —
|
||
cancelling a sweep mid-board is the race that guard exists to prevent.
|