Skip to content

feat(reporter): include config name in GitHub Actions summary header#9999

Open
mixelburg wants to merge 2 commits intovitest-dev:mainfrom
mixelburg:feat/github-actions-reporter-config-name
Open

feat(reporter): include config name in GitHub Actions summary header#9999
mixelburg wants to merge 2 commits intovitest-dev:mainfrom
mixelburg:feat/github-actions-reporter-config-name

Conversation

@mixelburg
Copy link
Copy Markdown
Contributor

Description

When name is set in the vitest config, append it to the job summary header so monorepo setups with multiple test suites can be distinguished at a glance.

Before:

## Vitest Test Report

After (when name: 'my-app' is set in config):

## Vitest Test Report (my-app)

Resolves #9992

Please don't delete this checklist! Before submitting the PR, please make sure you do the following:

  • It's really useful if your PR references an issue where it is discussed ahead of time.
  • Ideally, include a test that fails without this PR but passes with it.
  • Please, don't make changes to pnpm-lock.yaml unless you introduce a new test example.

Tests

  • Added a test in test/cli/test/reporters/github-actions.test.ts that verifies the config name appears in the summary header.

Documentation

No new API surface — name is an existing config field.

When `name` is set in vitest config, append it to the job summary header
so monorepo setups with multiple test suites can be distinguished:

  ## Vitest Test Report (my-app)

Closes vitest-dev#9992
@netlify
Copy link
Copy Markdown

netlify bot commented Mar 27, 2026

Deploy Preview for vitest-dev ready!

Built without sensitive environment variables

Name Link
🔨 Latest commit 58f7551
🔍 Latest deploy log https://app.netlify.com/projects/vitest-dev/deploys/69c6ff1b559d560008c387cf
😎 Deploy Preview https://deploy-preview-9999--vitest-dev.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@sheremet-va sheremet-va added the maybe automated User is likely an AI agent, or the content was generated by an AI assistant without user control label Mar 28, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

maybe automated User is likely an AI agent, or the content was generated by an AI assistant without user control

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Improve GitHub actions reporter with test name if set in config

2 participants