Skip to content

merge queue: embarking 9.3 (e44a662) and #48314 together#48317

Closed
mergify[bot] wants to merge 2 commits into
9.3from
mergify/merge-queue/7eb26bd14b
Closed

merge queue: embarking 9.3 (e44a662) and #48314 together#48317
mergify[bot] wants to merge 2 commits into
9.3from
mergify/merge-queue/7eb26bd14b

Conversation

@mergify

@mergify mergify Bot commented Jan 7, 2026

Copy link
Copy Markdown
Contributor

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

Branch 9.3 (e44a662) and #48314 are embarked together for merge.

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

Required conditions of queue default for merge:

Required conditions to stay in the queue:

---
checking_base_sha: e44a66269557556f6ebe8b124a5fc4f4c20dbff6
previous_failed_batches: []
pull_requests:
  - number: 48314
...

github-actions Bot and others added 2 commits January 7, 2026 15:15
Made with ❤️️ by updatecli
@github-actions

github-actions Bot commented Jan 7, 2026

Copy link
Copy Markdown
Contributor

🤖 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 Jan 7, 2026
@botelastic

botelastic Bot commented Jan 7, 2026

Copy link
Copy Markdown

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

@mergify mergify Bot closed this Jan 7, 2026
@mergify mergify Bot deleted the mergify/merge-queue/7eb26bd14b branch January 7, 2026 19:04
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