Skip to content

merge queue: embarking 2.28-maintenance (5763c35) and #13536 together#13545

Closed
mergify[bot] wants to merge 4 commits into2.28-maintenancefrom
mergify/merge-queue/4138afbdb0
Closed

merge queue: embarking 2.28-maintenance (5763c35) and #13536 together#13545
mergify[bot] wants to merge 4 commits into2.28-maintenancefrom
mergify/merge-queue/4138afbdb0

Conversation

@mergify
Copy link
Contributor

@mergify mergify bot commented Jul 24, 2025

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

Branch 2.28-maintenance (5763c35) and #13536 are embarked together for merge.

This pull request has been created by Mergify to speculatively check the mergeability of #13536.
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:

  • check-success=installer test on macos
  • check-success=installer test on ubuntu
  • check-success=tests on macos
  • check-success=tests on ubuntu
  • check-success=vm_tests
  • any of [🛡 GitHub branch protection]:
    • check-success = installer test on macos
    • check-neutral = installer test on macos
    • check-skipped = installer test on macos
  • any of [🛡 GitHub branch protection]:
    • check-success = installer test on ubuntu
    • check-neutral = installer test on ubuntu
    • check-skipped = installer test on ubuntu
  • any of [🛡 GitHub branch protection]:
    • check-success = tests on macos
    • check-neutral = tests on macos
    • check-skipped = tests on macos
  • any of [🛡 GitHub branch protection]:
    • check-success = tests on ubuntu
    • check-neutral = tests on ubuntu
    • check-skipped = tests on ubuntu

Required conditions to stay in the queue:

---
checking_base_sha: 5763c356a90fde94a3202512e7a1d1283840d54f
previous_failed_batches: []
pull_requests:
  - number: 13536
...

xokdvium and others added 4 commits July 24, 2025 23:13
(cherry picked from commit 04f6974)
This should provide more coverage for the build from master that
is being dogfooded.

(cherry picked from commit 3b3c021)
CI on release branches should be stable, otherwise backporting
might become flaky and unreliable. Dogfooding only really makes
sense for CI on master branch, where failures are not as tedious
to work around.
@xokdvium xokdvium closed this Jul 24, 2025
@mergify mergify bot deleted the mergify/merge-queue/4138afbdb0 branch July 24, 2025 20:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant