GRI-1766: wake the pull request's author when a gate fails #6
No reviewers
Labels
No labels
Area/Backend
Area/Database
Area/Docs
Area/Frontend
Area/Infra
Area/Security
Area/Tests
Area/Tooling
Compat/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Lang/Python
Lang/Rust
Lang/Shell
Lang/SQL
Lang/TypeScript
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Routing
Auto
Routing
Hold
Routing
Human
Status
Abandoned
Status
Blocked
Status
Need More Info
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
Grimoirix/grimoire-of-digital-signage!6
Loading…
Reference in a new issue
No description provided.
Delete branch "feature/GRI-1766-gate-failed-wake"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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:pull_requestonly, when at least one of the seven required gates isfailure. Cancelled is not failure, so a newer push that cancels the run sends nothing.advisoriesis excluded (ADR 0008).PAPERCLIP_GATE_FAILED_WAKE_LOGIN(nowvoidgazer).{"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 theneedsofci: it cannot change a branch's verdict.Configuration (already set, repository level)
PAPERCLIP_GATE_FAILED_HOOK_URLPAPERCLIP_GATE_FAILED_WAKE_LOGIN=voidgazerPAPERCLIP_GATE_FAILED_HOOK_SECRETTheir only authority is "start this one routine".
Tested
scripts/tests/pre-push-test.shandrepo-boundary --stagedpass. YAML-only change, so the Rust and front-end gates are left to this PR's CI.