Repository navigation
fix: evaluate the latest verified workflow check runs - #181
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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.