seriousben/Go Patch Coverage
Display golang patch test coverage on your pull requests.
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Stale
- License
- None
Inputs
| name | description | required | default |
|---|---|---|---|
| version | The version of go-patch-cover to use. | yes | v0.2.0 |
| coverage_filename | go coverage file for the code after change. Can be generated with any cover mode. Example generation: go test -coverprofile=coverage.out -covermode=count ./... | yes | coverage.out |
| diff_filename | Unified diff file of the patch to compute coverage for. Example generation: git diff -U0 --no-color origin/main > patch.diff | no | patch.diff |
| previous_coverage_filename | go coverage file for the code before changes. When not provided, previous coverage information will not be displayed. | no | prev_coverage.out |
| diff_enabled | Controls whether go-patch-cover action should create the diff file or not. | yes | true |
| prev_coverage_mode | The GitHub access token (e.g. secrets.GITHUB_TOKEN) used to create or update the comment. This defaults to {{ github.token }}. Modes: - git-notes: Use git notes: `refs/notes/coverage` to persist the coverage file on pushes. - file: Expect the file pointed to by the previous_coverage_filename input to already exist. | no | git-notes |
| github_token | The GitHub access token (e.g. secrets.GITHUB_TOKEN) used to create or update the comment. This defaults to {{ github.token }}. | no | ${{ github.token }} |
Outputs
no outputs