docs: replace Vitest JUnit upload with native @mergifyio/vitest reporter#10931
Merged
mergify[bot] merged 1 commit intomainfrom Apr 13, 2026
Conversation
The Vitest integration now uses the native `@mergifyio/vitest` reporter plugin instead of JUnit XML generation + upload. This aligns with the approach used by pytest-mergify and rspec-mergify. Fixes MRGFY-6881 Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> Change-Id: I84d3bc46744df1353f94b8843d85fc2e8c22d411 Claude-Session-Id: 0a6db61c-3fec-4343-9ae3-dfbc7b2e9e31
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 Vitest CI Insights documentation to use the native @mergifyio/vitest reporter instead of generating/uploading JUnit XML via a separate GitHub Action step.
Changes:
- Replace the JUnit report generation + upload-step instructions with
@mergifyio/vitestinstallation/configuration steps. - Update workflow guidance to only require exporting
MERGIFY_TOKENfor the test step. - Add an environment-variable reference table for the Vitest reporter.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
jd
approved these changes
Apr 8, 2026
sileht
approved these changes
Apr 8, 2026
Contributor
Merge Queue Status
This pull request spent 2 minutes 38 seconds in the queue, including 2 minutes 12 seconds running CI. Required conditions to merge
|
49 tasks
mergify
bot
deleted the
devs/kozlek/feat/vitest-mergify/I84d3bc46744df1353f94b8843d85fc2e8c22d411
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.
The Vitest integration now uses the native
@mergifyio/vitestreporterplugin instead of JUnit XML generation + upload. This aligns with the
approach used by pytest-mergify and rspec-mergify.
Fixes MRGFY-6881
Co-Authored-By: Claude Opus 4.6 (1M context) noreply@anthropic.com