You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: README.md
+2-1
Original file line number
Diff line number
Diff line change
@@ -82,11 +82,12 @@ This action requires the `pull-request: write` permission to add a comment to yo
82
82
| `working-directory` | The main path to search for coverage- and configuration files (adjusting this is especially useful in monorepos). | `./` |
83
83
| `json-summary-path` | The path to the json summary file. | `${working-directory}/coverage/coverage-summary.json` |
84
84
| `json-final-path` | The path to the json final file. | `${working-directory}/coverage/coverage-final.json` |
85
+
| `json-summary-compare-path` | The path to the json summary file to compare against. If given, will display a trend indicator and the difference in the summary. Respects the `working-directory` option. | undefined |
85
86
| `vite-config-path` | The path to the vite config file. Will check the same paths as vite and vitest | Checks pattern `${working-directory}/vite[st].config.{t\|mt\|ct\|j\|mj\|cj}s` |
86
87
| `github-token` | A GitHub access token with permissions to write to issues (defaults to `secrets.GITHUB_TOKEN`). | `${{ github.token }}` |
87
88
| `file-coverage-mode` | Defines how file-based coverage is reported. Possible values are `all`, `changes` or `none`. | `changes` |
89
+
| `file-coverage-root-path` | The root (or absolute) part of the path used within the json coverage reports to point to the covered files. You can change this if your reports were generated in a different context (e.g., a docker container) and the absolute paths don't match the current runner's workspace. Uses the runner's workspace path by default. | `${{ github.workspace }}` |
88
90
| `name` | Give the report a custom name. This is useful if you want multiple reports for different test suites within the same PR. Needs to be unique. | '' |
89
-
| `json-summary-compare-path` | The path to the json summary file to compare against. If given, will display a trend indicator and the difference in the summary. Respects the `working-directory` option. | undefined |
90
91
| `pr-number` | The number of the PR to post a comment to. When using the `push` trigger, you can set this option to "auto" to make the action automaticaly search of a PR with a matching `sha` value and comment on it. | If in the context of a PR, the number of that PR.<br/> If in the context of a triggered workflow, the PR of the triggering workflow. <br/>If no PR context is found, it defaults to `undefined` |
91
92
| `comment-on` | Specify where you want a comment to appear: "pr"for pull-request (if one can be found), "commit" for the commit in which context the action was run, or "none" for no comments. You can provide a comma-separated list of "pr" and "commit" to comment on both. | `pr` |
Copy file name to clipboardexpand all lines: action.yml
+5-1
Original file line number
Diff line number
Diff line change
@@ -24,9 +24,13 @@ inputs:
24
24
required: false
25
25
description: 'How to show summary for files coverage. Uses "changes" by default.'
26
26
default: changes
27
+
file-coverage-root-path:
28
+
required: false
29
+
description: 'The root (or absolute) part of the path used within the json coverage reports to point to the covered files. You can change this if your reports were generated in a different context (e.g., a docker container) and the absolute paths don''t match the current runner''s workspace. Uses the runner''s workspace path by default.'
30
+
default: ${{ github.workspace }}
27
31
working-directory:
28
32
required: false
29
-
description: 'Custom working directory'
33
+
description: 'Working directory where to look for the vite config file and the coverage report files. Uses "./" by default.'
0 commit comments