actions-marketplace-validations/Jest coverage referencing main branch existing summary
A github action to comment jest coverage diff on a PR using current branch vs already existing main branch summary
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Stale
- License
- None
- Runtime
- Deprecated runtime
Inputs
| name | description | required | default |
|---|---|---|---|
| accessToken | access token required to comment on a pr | — | ${{ github.token }} |
| fullCoverageDiff | get the full coverage with diff or only the diff | — | false |
| runCommand | custom command to get json-summary | — | npx jest --coverage --coverageReporters="json-summary" --coverageDirectory="./" |
| delta | Difference between the old and final test coverage | — | 100 |
| total_delta | Difference between the old and final test coverage at the total level | — | — |
| useSameComment | While commenting on the PR update the exisiting comment | — | false |
| mainBranchCoverageSummaryFileName | file name of main branch summary (master) | — | develop-coverage-summary.json |
| additionalCommentInfo | Additional string that will be concatenated to comment | — | — |
| codeCoverageDirectory | code coverage summary location defaults to coverage-summary.json | — | coverage-summary.json |
Outputs
no outputs