Skip to content

Check the CI gate against check-runs, not the legacy status API #8

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
leggetter merged 1 commit into from
Aug 12, 2026
Merged

Check the CI gate against check-runs, not the legacy status API #8

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 7 additions & 2 deletions skills/hermes-hookdeck-release/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -198,10 +198,15 @@ only for a first-time contributor or an exceptionally large contribution.
6. **CI:**

```bash
gh api "repos/hookdeck/hermes-hookdeck/commits/$(git rev-parse origin/main)/status" --jq .state
gh api "repos/hookdeck/hermes-hookdeck/commits/$(git rev-parse origin/main)/check-runs" \
--jq '.check_runs[] | "\(.name): \(.status)/\(.conclusion // "-")"'
```

Do not release on `failure`, or on `pending` for required checks.
Every run must be `completed/success`. Do not release otherwise.

Ask for **check-runs**, not `/status`. The latter reports the legacy commit
Status API, which this repo does not use — with no statuses recorded it
answers `pending` forever, so it reads as a red gate on a green `main`.

## Safety and governance

Expand Down
Loading