docs: rewrite RSpec page for rspec-mergify gem integration#10813
Merged
mergify[bot] merged 1 commit intomainfrom Apr 3, 2026
Merged
Conversation
Contributor
Merge ProtectionsYour pull request matches the following merge protections and will not be merged until they are valid. 🟢 🤖 Continuous IntegrationWonderful, this rule succeeded.
🟢 👀 Review RequirementsWonderful, this rule succeeded.
🟢 Enforce conventional commitWonderful, this rule succeeded.Make sure that we follow https://www.conventionalcommits.org/en/v1.0.0/
🟢 🔎 ReviewsWonderful, this rule succeeded.
🟢 📕 PR descriptionWonderful, this rule succeeded.
|
There was a problem hiding this comment.
Pull request overview
Updates the CI Insights documentation for RSpec to recommend the rspec-mergify gem as the primary integration path (similar to the existing pytest-mergify docs), while keeping the previous JUnit XML + GitHub Action upload flow as an alternative.
Changes:
- Rewrites the RSpec CI Insights page to focus on
rspec-mergifyinstallation and minimal workflow setup (exportMERGIFY_TOKEN). - Adds an “Environment Variables” section describing configuration options for the gem.
- Preserves the legacy approach as an “Alternative: Manual JUnit XML Upload” section with inline YAML examples.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
kozlek
previously approved these changes
Apr 2, 2026
JulianMaurin
previously approved these changes
Apr 2, 2026
Contributor
Merge Queue Status
This pull request spent 14 hours 12 minutes 55 seconds in the queue, including 2 minutes 7 seconds running CI. Required conditions to merge
ReasonPull request #10813 has been dequeued The pull request rule doesn't match anymore HintYou should look at the reason for the failure and decide if the pull request needs to be fixed or if you want to requeue it. |
49 tasks
jd
previously requested changes
Apr 3, 2026
This was referenced Apr 3, 2026
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
sileht
force-pushed
the
devs/sileht/rspec/I35f8ea6dee585b97c541796c4776406c500a4399
branch
from
d01aaf1 to
dfcbfac
Compare
mergify
bot
dismissed stale reviews from jd and JulianMaurin
Pull request has been modified.
jd
approved these changes
Apr 3, 2026
JulianMaurin
approved these changes
Apr 3, 2026
Contributor
Merge Queue Status
This pull request spent 2 minutes 25 seconds in the queue, including 2 minutes 11 seconds running CI. Required conditions to merge
|
49 tasks
mergify
bot
deleted the
devs/sileht/rspec/I35f8ea6dee585b97c541796c4776406c500a4399
branch
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.
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