actions-marketplace-validations/Jest coverage report with nix support
Track your code coverage in each pull request.
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Stale
- License
- None
Inputs
| name | description | required | default |
|---|---|---|---|
| github-token | A github access token | yes | ${{ github.token }} |
| test-script | A custom npm script to get coverage | no | npx jest |
| threshold | Coverage threshold. If total coverage is less than threshold, PR will be rejected | no | — |
| working-directory | Custom working directory | no | — |
| icons | Which icons to use. Available choices: emoji, ascii | no | emoji |
| annotations | What type of annotations show. Options: none, coverage, failed-tests, all | no | all |
| package-manager | Which package manager to use; can be `npm`, `yarn`, or `pnpm` | no | npm |
| skip-step | `none` for running all steps, `install` to skip installing dependencies or `all` to skip installing dependencies and running the test script | no | none |
| custom-title | Sets the title of the coverage report comment in Github. | no | — |
| coverage-file | Path to file the a previously generated report.json file. (bypasses running the test again) | no | — |
| base-coverage-file | Path to the report.json file to compare against. This should be from the branch the PR is merging into. | no | — |
| prnumber | Pull Request number for this commit. Use if your action is running in a PR, but non on the pull_request event, so that you do not get multiple comments. | no | — |
| output | What output should action produce? `comment` - add comment to PR, `report-markdown` - report markdown text in "outputs.report". | no | comment |
Outputs
| name | description |
|---|---|
| report | Generated markdown report. Exists only if input option "output" is set to "report-markdown". |