Skip to content

fix: evaluate the latest verified workflow check runs - #181

Merged
Yehonal merged 2 commits into
mainfrom
fix/latest-check-runs
Nov 17, 2026
Merged

Yehonal merged 2 commits into
mainfrom
fix/latest-check-runs

Conversation

@Yehonal

@Yehonal Yehonal commented Nov 17, 2026

Copy link
Copy Markdown
Collaborator

A cancelled check from a superseded run could block a PR even when a newer run of the same head and workflow succeeded. Merge policy now selects the latest verified run per workflow and check name, reports superseded runs as informational, and keeps the block for a current result other than SUCCESS or SKIPPED. Required checks use the same selection and retain provider constraints.

The adapter combines exact-head REST and GraphQL observations using immutable check IDs and workflow identities. It handles partial reruns per check, keeps distinct workflows and legacy status contexts separate, and preserves a blocking result when observations disagree. GraphQL history paginates on the exact commit; incomplete, ambiguous or bounded-out observations cannot hide a blocker. Informational superseded history does not change the merge-plan digest.

Validation: 54 adapter and merge-policy tests passed, plus 23 integration checks after merging current main. Fixtures cover superseded cancellations, current failures and queued runs, same-name workflows, legacy status changes between reads, partial reruns, immutable identity, 101-result pagination, and incomplete observations. Module/documentation, privacy and version checks passed. Independent review READY on f50f5d8. Version 0.47.23.

@Yehonal
Yehonal merged commit 3360ec8 into main Nov 17, 2026
20 checks 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