Require passing CI for auto-merge and refresh the gate after retries - #267
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
1 participant
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.
Add a
Required checksworkflow that waits for link and spelling checks on documentation changes, and all nine existing PR workflows on code changes. This provides a single status for the repository's auto-merge requirement.Add a completion-triggered retry workflow that reruns the original PR check after a CI retry succeeds. It verifies the current open PR commit, supports fork PRs, handles completion races, and avoids retry loops. The privileged listener reads GitHub metadata without checking out PR code.
Validation passed with actionlint and 17 local gate/retry behavior checks. Existing test commands and path filters are preserved; the nightly PyTorch test command remains disabled as before.