{{ message }}
Repository navigation
merge queue: checking #61734 + #61773 together on develop (f01723b) - #61789
Closed
mergify[bot] wants to merge 12 commits into
Closed
mergify[bot] wants to merge 12 commits into
mergify[bot] wants to merge 12 commits into
Conversation
This was referenced Oct 21, 2026
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.

Note
This is a merge queue draft opened by Mergify. Nobody needs to act on it.
Mergify opened it for batch hallowed-salers-xtw0dy of the
defaultqueue, to test #61734 and #61773 before they merge intodevelop.What this draft tests
Mergify checks that #61734 and #61773 still pass CI on top of
develop. CI runs on this draft's code, built in this order:developatf01723bThis batch comes from splitting a batch whose checks failed: Mergify checks smaller batches to find which pull request is responsible. The batches it was split from are listed below.
✨ Where it stands: closed
Checks failed and are being retried (attempt 1/1).
Follow the
defaultqueue in the dashboardWhat happens next
Bisected from a failed batch:
Metadata for CI tooling, read by
mergify ciRequired conditions of queue rule
defaultfor mergecheck-success=Python Unit Tests (3)#review-threads-unresolved = 0[🛡 GitHub branch protection]check-success=Patch Testcheck-success=Python Unit Tests (1)check-success=Python Unit Tests (2)check-success=Python Unit Tests (4)github-review-approved[🛡 GitHub branch protection]Required conditions to stay in the queue
#review-threads-unresolved = 0[🛡 GitHub branch protection]base~=^(develop|version-15-hotfix|version-16-hotfix)$check-success=Check Commit Titlescheck-success=lintersgithub-review-approved[🛡 GitHub branch protection]label!=dont-merge