Add verified winners and baseline setup - #1
Merged
Merged
Conversation
269394628
marked this pull request as ready for review
July 27, 2026 08:00
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.
What changed
Why
A non-empty patch could previously be selected as the winner even when its configured checks failed. Detached worktrees also had no supported dependency setup stage, and results could not distinguish pre-existing test failures from candidate regressions.
Impact
PatchLeague now reports no winner unless every configured check passes. Existing configurations remain valid because the new setup stage defaults to an empty list. Users can opt into setup commands such as
npm cioruv sync --frozen.Validation
npm run verifynpm pack --dry-rungit diff --check