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
| Time to First Response | The duration from creation to the initial comment or review.\*|
23
+
| Time to First Review (PRs Only) | The duration from creation to the first submitted review.\*|
23
24
| Time to Close | The period from creation to closure.\*|
24
25
| Time to Answer (Discussions Only) | The time from creation to an answer. |
25
26
| Time in Label | The duration from label application to removal, requires `LABELS_TO_MEASURE` env variable. |
@@ -108,18 +109,18 @@ All feedback regarding our GitHub Actions, as a whole, should be communicated th
108
109
## Use as a GitHub Action
109
110
110
111
1. Create a repository to host this GitHub Action or select an existing repository. This is easiest if it is the same repository as the one you want to measure metrics on.
111
-
2. Select a best fit workflow file from the [examples directory](./docs/example-workflows.md) for your use case.
112
-
3. Copy that example into your repository (from step 1) and into the proper directory for GitHub Actions: `.github/workflows/` directory with the file extension `.yml` (ie. `.github/workflows/issue-metrics.yml`)
113
-
4. Edit the values (`SEARCH_QUERY`, `assignees`) from the sample workflow with your information. See the [SEARCH_QUERY](./docs/search-query.md) section for more information on how to configure the search query.
114
-
5. If you are running metrics on a repository other than the one where the workflow file is going to be, then update the value of `GH_TOKEN`.
112
+
1. Select a best fit workflow file from the [examples directory](./docs/example-workflows.md) for your use case.
113
+
1. Copy that example into your repository (from step 1) and into the proper directory for GitHub Actions: `.github/workflows/` directory with the file extension `.yml` (ie. `.github/workflows/issue-metrics.yml`)
114
+
1. Edit the values (`SEARCH_QUERY`, `assignees`) from the sample workflow with your information. See the [SEARCH_QUERY](./docs/search-query.md) section for more information on how to configure the search query.
115
+
1. If you are running metrics on a repository other than the one where the workflow file is going to be, then update the value of `GH_TOKEN`.
115
116
- Do this by creating a [GitHub API token](https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/managing-your-personal-access-tokens#creating-a-personal-access-token-classic) with permissions to read the repository and write issues.
116
117
- Then take the value of the API token you just created, and [create a repository secret](https://docs.github.com/en/actions/security-guides/encrypted-secrets) where the name of the secret is `GH_TOKEN` and the value of the secret the API token.
117
118
- Then finally update the workflow file to use that repository secret by changing `GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}` to `GH_TOKEN: ${{ secrets.GH_TOKEN }}`. The name of the secret can really be anything. It just needs to match between when you create the secret name and when you refer to it in the workflow file.
118
119
- Help on verifying your token's access to your repository [in the docs directory](docs/verify-token-access-to-repository.md)
119
-
6. If you want the resulting issue with the metrics in it to appear in a different repository other than the one the workflow file runs in, update the line `token: ${{ secrets.GITHUB_TOKEN }}` with your own GitHub API token stored as a repository secret.
120
+
1. If you want the resulting issue with the metrics in it to appear in a different repository other than the one the workflow file runs in, update the line `token: ${{ secrets.GITHUB_TOKEN }}` with your own GitHub API token stored as a repository secret.
120
121
- This process is the same as described in the step above. More info on creating secrets can be found [in the GitHub docs security guide on encrypted secrets](https://docs.github.com/en/actions/security-guides/encrypted-secrets).
121
-
7. Commit the workflow file to the default branch (often `master` or `main`)
122
-
8. Wait for the action to trigger based on the `schedule` entry or manually trigger the workflow as shown in the [documentation](https://docs.github.com/en/actions/using-workflows/manually-running-a-workflow).
122
+
1. Commit the workflow file to the default branch (often `master` or `main`)
123
+
1. Wait for the action to trigger based on the `schedule` entry or manually trigger the workflow as shown in the [documentation](https://docs.github.com/en/actions/using-workflows/manually-running-a-workflow).
123
124
124
125
### Configuration
125
126
@@ -157,6 +158,7 @@ This action can be configured to authenticate with GitHub App Installation or Pe
157
158
| `HIDE_TIME_TO_ANSWER` | False | False | If set to `true`, the time to answer a discussion will not be displayed in the generated Markdown file. |
158
159
| `HIDE_TIME_TO_CLOSE` | False | False | If set to `true`, the time to close will not be displayed in the generated Markdown file. |
159
160
| `HIDE_TIME_TO_FIRST_RESPONSE` | False | False | If set to `true`, the time to first response will not be displayed in the generated Markdown file. |
161
+
| `HIDE_TIME_TO_FIRST_REVIEW` | False | False | If set to `true`, the time to first review will not be displayed in the generated Markdown file. |
160
162
| `HIDE_STATUS` | False | True | If set to `true`, the status column will not be shown |
161
163
| `HIDE_CREATED_AT` | False | True | If set to `true`, the creation timestamp will not be displayed in the generated Markdown file. |
162
164
| `HIDE_PR_STATISTICS` | False | True | If set to `true`, PR comment statistics (mean, median, 90th percentile, and individual PR comment counts) will not be displayed in the generated Markdown file. |
@@ -173,7 +175,7 @@ This action can be configured to authenticate with GitHub App Installation or Pe
173
175
| `REPORT_TITLE` | False | `"Issue Metrics"` | Title to have on the report issue. |
174
176
| `SEARCH_QUERY` | True | `""` | The query by which you can filter issues/PRs which must contain a `repo:`, `org:`, `owner:`, or a `user:` entry. For discussions, include `type:discussions` in the query. |
175
177
| `GROUP_BY` | False | `""` | Group items in the report by the specified field. Supported values: `author`, `assignee`. When set, items will be grouped into separate sections by the chosen field. |
176
-
| `SORT_BY` | False | `""` | Sort items in the report by the specified field. Supported values: `time_to_close`, `time_to_first_response`, `time_to_answer`, `time_in_draft`, `created_at`. When set, items will be sorted by the chosen metric. |
178
+
| `SORT_BY` | False | `""` | Sort items in the report by the specified field. Supported values: `time_to_close`, `time_to_first_response`, `time_to_first_review`, `time_to_answer`, `time_in_draft`, `created_at`. When set, items will be sorted by the chosen metric. |
177
179
| `SORT_ORDER` | False | `asc` | Sort order for the items. Supported values: `asc`(ascending), `desc` (descending). Only applies when `SORT_BY` is set. |
0 commit comments