Skip to content

feat: name a PR's failing checks - #161

Merged
brtkwr merged 1 commit into
mainfrom
feat/failing-check-names
Oct 28, 2026
Merged

brtkwr merged 1 commit into
mainfrom
feat/failing-check-names

Conversation

@brtkwr

@brtkwr brtkwr commented Oct 28, 2026

Copy link
Copy Markdown
Collaborator

A PR whose checks fail now says which ones, in the preview's PR lines and the ^O list:

```
✗ checkout-api#12946 … · checks failing: DeepSource: Python
```

It shows at most three names, then `+N`. "Ready to merge · optional checks failing" names them too.

How: the GitHub lookup also asks for the head commit's checks (up to 50 per PR). A check run counts as failing when its conclusion is failure, timed out, cancelled, action required or startup failure; a commit status, when it's failure or error.

Checked against GitHub: the query works on real PRs. checkout-api PR 12946 reads `checks failing: DeepSource: Python`, and two passing ccs PRs are unchanged.

Test: `TestGhPRBatchReadsPartialAnswers` now covers a failing check run, a passing one and a failing commit status, and the status text.

🤖 Generated with Claude Code

https://claude.ai/code/session_01QUnP8jVL2NG9cWmohJTyun

"checks failing" now says which: "checks failing: test, ci/deploy", at
most three then +N, and the same on "optional checks failing". The PR
lookup also asks for the head commit's check runs and commit statuses.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01QUnP8jVL2NG9cWmohJTyun
@brtkwr
brtkwr enabled auto-merge October 28, 2026 11:12
@brtkwr
brtkwr merged commit 20116a2 into main Oct 28, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant