GRI-1766: wake the pull request's author when a gate fails #6

Merged
vivy merged 2 commits from feature/GRI-1766-gate-failed-wake into dev 2026-11-06 00:26:13 +00:00
Owner

Board issue: GRI-1766. The product owner asked: when voidgazer's pull request fails a gate, wake voidgazer with "gate X failed", so it fixes and pushes until the branch is green.

What this adds

One job, notify-gate-failed, after the seven gates:

  • Runs on pull_request only, when at least one of the seven required gates is failure. Cancelled is not failure, so a newer push that cancels the run sends nothing. advisories is excluded (ADR 0008).
  • Fires only when the PR author equals the repo variable PAPERCLIP_GATE_FAILED_WAKE_LOGIN (now voidgazer).
  • Posts {"event":"gate_failed","message":"gate cargo fmt failed; ...","failed":[...],"pull_request":n,"head_ref":...,"head_sha":...,"run_url":...} to a Paperclip routine webhook. The routine is assigned to voidgazer and creates an issue for it — that issue is the wake.
  • continue-on-error, not in the needs of ci: it cannot change a branch's verdict.

Configuration (already set, repository level)

  • variable PAPERCLIP_GATE_FAILED_HOOK_URL
  • variable PAPERCLIP_GATE_FAILED_WAKE_LOGIN = voidgazer
  • secret PAPERCLIP_GATE_FAILED_HOOK_SECRET

Their only authority is "start this one routine".

Tested

  • The board end: a manual event for PR #5 created voidgazer's issue (HTTP 202).
  • The payload logic, run locally with simulated job results: right gate names; another author sends nothing.
  • scripts/tests/pre-push-test.sh and repo-boundary --staged pass. YAML-only change, so the Rust and front-end gates are left to this PR's CI.
  • Not yet tested on a real red run. The first one is voidgazer's next push to PR #5.
Board issue: GRI-1766. The product owner asked: when voidgazer's pull request fails a gate, wake voidgazer with "gate X failed", so it fixes and pushes until the branch is green. ## What this adds One job, `notify-gate-failed`, after the seven gates: - Runs on `pull_request` only, when at least one of the seven required gates is `failure`. Cancelled is not failure, so a newer push that cancels the run sends nothing. `advisories` is excluded (ADR 0008). - Fires only when the PR author equals the repo variable `PAPERCLIP_GATE_FAILED_WAKE_LOGIN` (now `voidgazer`). - Posts `{"event":"gate_failed","message":"gate cargo fmt failed; ...","failed":[...],"pull_request":n,"head_ref":...,"head_sha":...,"run_url":...}` to a Paperclip routine webhook. The routine is assigned to voidgazer and creates an issue for it — that issue is the wake. - `continue-on-error`, not in the `needs` of `ci`: it cannot change a branch's verdict. ## Configuration (already set, repository level) - variable `PAPERCLIP_GATE_FAILED_HOOK_URL` - variable `PAPERCLIP_GATE_FAILED_WAKE_LOGIN` = `voidgazer` - secret `PAPERCLIP_GATE_FAILED_HOOK_SECRET` Their only authority is "start this one routine". ## Tested - The board end: a manual event for PR #5 created voidgazer's issue (HTTP 202). - The payload logic, run locally with simulated job results: right gate names; another author sends nothing. - `scripts/tests/pre-push-test.sh` and `repo-boundary --staged` pass. YAML-only change, so the Rust and front-end gates are left to this PR's CI. - Not yet tested on a real red run. The first one is voidgazer's next push to PR #5.
GRI-1766: wake the pull request's author when a gate fails
Some checks failed
CI / the pre-push hook (pull_request) Successful in 10s
CI / cargo fmt (pull_request) Successful in 10s
CI / cargo deny advisories (pull_request) Failing after 1m2s
CI / repository boundary (pull_request) Successful in 7s
CI / cargo clippy (pull_request) Successful in 9m37s
CI / cargo test (pull_request) Successful in 9m45s
CI / frontend-web (pull_request) Successful in 9m37s
CI / cargo deny (pull_request) Failing after 15m8s
CI / CI (pull_request) Has been cancelled
CI / Notify gate failed (pull_request) Has been cancelled
92ff177ddf
GRI-1766: re-run CI, cargo deny hit its 15 min timeout
Some checks failed
CI / cargo fmt (pull_request) Successful in 8s
CI / the pre-push hook (pull_request) Successful in 10s
CI / cargo deny (pull_request) Successful in 59s
CI / cargo deny advisories (pull_request) Failing after 59s
CI / repository boundary (pull_request) Successful in 10s
CI / cargo clippy (pull_request) Successful in 9m42s
CI / cargo test (pull_request) Successful in 9m40s
CI / frontend-web (pull_request) Successful in 9m39s
CI / Notify gate failed (pull_request) Has been skipped
CI / CI (pull_request) Successful in 4s
fb75bbe5b7
vivy merged commit bddd627f96 into dev 2026-11-06 00:26:13 +00:00
vivy deleted branch feature/GRI-1766-gate-failed-wake 2026-11-06 00:26:14 +00:00
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
Grimoirix/grimoire-of-digital-signage!6
No description provided.