cli/pkg/cmd/pr/status/fixtures
Kynan Ware 1c274a8a56 fix(pr status): don't count cancelled checks as failures
When a GitHub Actions workflow uses concurrency with cancel-in-progress,
cancelled runs were counted as failures in `gh pr status` and
`gh pr view`, even when a newer run for the same check name succeeded.
The GitHub web UI and `gh pr checks` both handle this correctly.

Three changes fix this:

1. Add a `cancelled` check status category. Cancelled runs are now
   excluded from all summary counts (passing/failing/pending) and
   subtracted from the total, matching the web UI behavior.

2. Move `eliminateDuplicates` from pkg/cmd/pr/checks to
   `api.EliminateDuplicateChecks` (exported). The function operates
   entirely on `api.CheckContext` and is now shared by both `pr checks`
   and `ChecksStatus()` (used by `pr status` and `pr view`).

3. Apply deduplication in the `ChecksStatus()` slow path, keeping only
   the most recent run per check name — consistent with `pr checks`.

Fixes #12895

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
2026-03-11 12:33:31 -06:00
..
prStatus.json Include auto-merge information in gh pr status (#7386) 2023-05-10 08:32:05 +12:00
prStatusChecks.json fix(pr status): don't count cancelled checks as failures 2026-03-11 12:33:31 -06:00
prStatusChecksWithStatesByCount.json Add cmd test for pr status with counts by state 2023-05-24 16:00:34 +02:00
prStatusCurrentBranch.json Isolate pr status command 2020-07-31 19:07:30 +02:00
prStatusCurrentBranchClosed.json Remove unnecessary commits stubs from fixtures 2021-05-21 17:37:21 +02:00
prStatusCurrentBranchClosedOnDefaultBranch.json Isolate pr status command 2020-07-31 19:07:30 +02:00
prStatusCurrentBranchMerged.json Remove unnecessary commits stubs from fixtures 2021-05-21 17:37:21 +02:00
prStatusCurrentBranchMergedOnDefaultBranch.json Isolate pr status command 2020-07-31 19:07:30 +02:00