feat(github-actions): include project name in job summary heading#10099
Draft
feat(github-actions): include project name in job summary heading#10099
Conversation
4 tasks
✅ Deploy Preview for vitest-dev ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Agent-Logs-Url: https://github.com/vitest-dev/vitest/sessions/1bf8e14a-923e-4427-a9ff-f77391f357e9 Co-authored-by: sheremet-va <16173870+sheremet-va@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Enhance GitHub actions reporter with config test name
feat(github-actions): include project name in job summary heading
Apr 8, 2026
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.
In monorepos where multiple vitest configs run in the same CI job, all summaries are written to the same
$GITHUB_STEP_SUMMARYfile and produce identical## Vitest Test Reportheadings — making it impossible to tell them apart at a glance.Changes
renderSummary– accepts an optionalnameparameter; when set, heading becomes## Vitest Test Report (name)instead of the static fallbackonTestRunEnd– passesthis.ctx.config.nametorenderSummaryautomatically; no reporter option change neededUsage
Set
namein your vitest config:Each suite's summary will now be headed
## Vitest Test Report (web),## Vitest Test Report (api), etc., making the job summary scannable in a monorepo context.