Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: auto-enable github-actions reporter #1

Merged

Conversation

hi-ogawa
Copy link
Owner

@hi-ogawa hi-ogawa commented Feb 6, 2024

Description

Testing auto enable to see what happens on Vitest repo CI.

todo

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. If the feature is substantial or introduces breaking changes without a discussion, PR might be closed.
  • 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

  • Run the tests with pnpm test:ci.

Documentation

  • If you introduce new functionality, document it. You can run documentation with pnpm run docs command.

Changesets

  • Changes in changelog are generated from PR name. Please, make sure that it explains your changes in an understandable manner. Please, prefix changeset messages with feat:, fix:, perf:, docs:, or chore:.

@hi-ogawa hi-ogawa changed the title feat(vitest): auto enable github-actions reporter (wip) auto enable github-actions reporter Feb 6, 2024
@hi-ogawa hi-ogawa changed the title (wip) auto enable github-actions reporter feat: auto-enable github-actions reporter Feb 6, 2024
@hi-ogawa hi-ogawa merged commit 805a5e3 into feat-github-actions-reporter Feb 7, 2024
13 of 15 checks passed
@hi-ogawa hi-ogawa deleted the feat-github-actions-reporter-automatic branch February 7, 2024 01:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant