Skip to content

merge queue: embarking 9.3 (efc684b) and #49934 together#49936

Closed
mergify[bot] wants to merge 2 commits into9.3from
mergify/merge-queue/a1ed053764
Closed

merge queue: embarking 9.3 (efc684b) and #49934 together#49936
mergify[bot] wants to merge 2 commits into9.3from
mergify/merge-queue/a1ed053764

Conversation

@mergify
Copy link
Copy Markdown
Contributor

@mergify mergify bot commented Apr 4, 2026

🎉 This pull request has been checked successfully and will be merged soon. 🎉

Branch 9.3 (efc684b) and #49934 are embarked together for merge.

This pull request has been created by Mergify to speculatively check the mergeability of #49934.
You don't need to do anything. Mergify will close this pull request automatically when it is complete.

Required conditions of queue rule default for merge:

Required conditions to stay in the queue:

---
checking_base_sha: efc684bf5bd56468ddeb4512b1911fb31ffb2c2d
previous_failed_batches: []
pull_requests:
  - number: 49934
    scopes: []
scopes: []
...

github-actions bot and others added 2 commits April 4, 2026 12:14
@github-actions
Copy link
Copy Markdown
Contributor

github-actions bot commented Apr 4, 2026

🤖 GitHub comments

Just comment with:

  • run docs-build : Re-trigger the docs validation. (use unformatted text in the comment!)

@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label Apr 4, 2026
@botelastic
Copy link
Copy Markdown

botelastic bot commented Apr 4, 2026

This pull request doesn't have a Team:<team> label.

@mergify mergify bot closed this Apr 5, 2026
@mergify mergify bot deleted the mergify/merge-queue/a1ed053764 branch April 5, 2026 00:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

needs_team Indicates that the issue/PR needs a Team:* label

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants