|
7 | 7 |
|
8 | 8 | # check_done
|
9 | 9 |
|
10 |
| -A command-line tool that validates the completeness of GitHub project items (issue or pull request) in your specified project status that represents done project items. |
| 10 | +Check_done is a command line tool to check that GitHub issues and pull requests in a project board with a status of "Done" are really done. |
11 | 11 |
|
12 |
| -Current checks are: |
| 12 | +It checks that: |
13 | 13 |
|
14 |
| -- Project item is closed. |
15 |
| -- Project item has an assignee. |
16 |
| -- Project item has a set milestone. |
17 |
| -- Project item has all tasks completed (list with checkboxes in the description). |
18 |
| -- Pull request has a closing issue reference. |
| 14 | +- It is closed. |
| 15 | +- It has an assignee. |
| 16 | +- It is assigned to a milestone. |
| 17 | +- All tasks are completed (checkboxes in the description). |
19 | 18 |
|
20 |
| -This ensures a consistent quality on done project items, and helps to notice if they were accidentally deemed to be done too early. |
| 19 | +Additionally, for pull requests, it checks if they reference an issue. |
| 20 | + |
| 21 | +This ensures a consistent quality on done issues and pull requests, and helps to notice if they were accidentally deemed to be done too early. |
21 | 22 |
|
22 | 23 | ## Installation
|
23 | 24 |
|
24 | 25 | In order to gain access to your project board, issues, and pull requests, check_done needs to be authorized. The exact way to do that depends on whether your project belongs to a GitHub user or organization.
|
25 | 26 |
|
26 | 27 | For user projects, [create a personal access token](https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/managing-your-personal-access-tokens) with the permission: `read:project`.
|
27 | 28 |
|
28 |
| -For organization projects, follow the instructions to [Installing a GitHub App from a third party](https://docs.github.com/en/apps/using-github-apps/installing-a-github-app-from-a-third-party) using the [Check_done app](https://github.com/apps/check-done-app). |
29 |
| - |
30 |
| -Remember the **app ID** and **private key** of the installed app. |
| 29 | +For organization projects, follow the instructions to [Installing a GitHub App from a third party](https://docs.github.com/en/apps/using-github-apps/installing-a-github-app-from-a-third-party) using the [Check_done app](https://github.com/apps/check-done-app). Remember the **app ID** and **private key** of the installed app in order to use for configuration. |
31 | 30 |
|
32 | 31 | ## Configuration
|
33 | 32 |
|
@@ -69,7 +68,7 @@ In order to avoid having to commit tokens and keys into your repository, you can
|
69 | 68 | personal_access_token: ${MY_PERSONAL_ACCESS_TOKEN_ENVVAR}
|
70 | 69 | ```
|
71 | 70 |
|
72 |
| -### Changing the project status name to check |
| 71 | +### Changing the project status to check |
73 | 72 |
|
74 | 73 | By default, check_done checks all issues and pull requests in the last selectable project status. If you left the default names when creating the GitHub project board, this would be the `"✅ Done"` project status.
|
75 | 74 |
|
|
0 commit comments