Skip to content

merge queue: embarking main (b20a893) and #10813 together#10841

Closed
mergify[bot] wants to merge 2 commits intomainfrom
mergify/merge-queue/e5195a67da
Closed

merge queue: embarking main (b20a893) and #10813 together#10841
mergify[bot] wants to merge 2 commits intomainfrom
mergify/merge-queue/e5195a67da

Conversation

@mergify
Copy link
Copy Markdown
Contributor

@mergify mergify bot commented Apr 3, 2026

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

Branch main (b20a893) and #10813 are embarked together for merge.

This pull request has been created by Mergify to speculatively check the mergeability of #10813.
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: b20a8938fc7badc445b563334fc8469691034af7
previous_failed_batches: []
pull_requests:
  - number: 10813
    scopes: []
scopes: []
...

sileht and others added 2 commits April 3, 2026 08:58
Replace the JUnit XML upload approach with rspec-mergify as the primary
integration method. The gem automatically uploads test results to CI
Insights when MERGIFY_TOKEN is set, matching the pytest-mergify pattern.

The previous JUnit XML approach is preserved as an "Alternative" section.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Change-Id: I35f8ea6dee585b97c541796c4776406c500a4399
@mergify mergify bot deployed to Mergify Merge Protections April 3, 2026 08:04 Active
@mergify mergify bot closed this Apr 3, 2026
@mergify mergify bot deleted the mergify/merge-queue/e5195a67da branch April 3, 2026 08:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

1 participant