ditkrg/todo-to-issue-action
4
0
Fork 0
mirror of https://github.com/ditkrg/todo-to-issue-action.git synced 2026-01-23 06:16:43 +00:00
Code Issues Packages Projects Releases Wiki Activity

Update README.md

Browse Source
This commit is contained in:
alstr 2022-10-27 14:40:06 +01:00
parent 0bc639834b
commit 951fc4f740
2 changed files with 56 additions and 18 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
.github/workflows/todo.yml vendored
View File

@ -16,7 +16,6 @@ jobs:
- uses: "actions/checkout@v3"
- name: "TODO to Issue"
uses: "alstr/todo-to-issue-action@master"
id: "todo"
env:
MANUAL_COMMIT_REF:
${{ inputs.MANUAL_COMMIT_REF }}

73
README.md
View File

@ -1,6 +1,8 @@
# TODO to Issue Action
This action will convert newly committed TODO comments to GitHub issues on push. It will also optionally close the issues if the TODOs are removed in a future commit. Works with almost any programming language.
This action will convert newly committed TODO comments to GitHub issues on push. It will also optionally close the issues if the TODOs are removed in a future commit.
Todo to Issue works with almost any programming language.
## Usage
@ -29,16 +31,15 @@ Multiline TODOs are supported, with additional lines inserted into the issue bod
Create a `workflow.yml` file in your `.github/workflows` directory like:
```yml
name: "Workflow"
name: "Run Todo to Issue"
on: ["push"]
jobs:
build:
runs-on: "ubuntu-latest"
steps:
- uses: "actions/checkout@master"
- uses: "actions/checkout@v3"
- name: "TODO to Issue"
uses: "alstr/todo-to-issue-action@v4"
id: "todo"
```
See [Github's workflow syntax](https://help.github.com/en/actions/reference/workflow-syntax-for-github-actions) for further details on this file.
@ -47,7 +48,6 @@ The workflow file takes the following optional inputs:
| Input | Required | Description |
|------------------|----------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| `TOKEN` | No | The GitHub access token to allow us to retrieve, create and update issues for your repo. Default: `${{ github.token }}`. |
| `CLOSE_ISSUES` | No | Optional boolean input that specifies whether to attempt to close an issue when a TODO is removed. Default: `true`. |
| `AUTO_P` | No | Optional boolean input that specifies whether to format each line in multiline TODOs as a new paragraph. Default: `true`. |
| `IGNORE` | No | Optional string input that provides comma-delimited regular expressions that match files in the repo that we should not scan for TODOs. By default, we will scan all files. |
@ -57,11 +57,9 @@ The workflow file takes the following optional inputs:
These can be specified in `with` in the workflow file.
There are additional inputs if you want to be able to assign issues to projects. Consult the relevant section below for more details.
### Considerations
* TODOs are found by analysing the difference between the new commit and its previous one (i.e., the diff). That means that if this action is implemented during development, any existing TODOs will not be detected. For them to be detected, you would have to remove them, commit, put them back, and commit again.
* TODOs are found by analysing the difference between the new commit and its previous one (i.e., the diff). That means that if this action is implemented during development, any existing TODOs will not be detected. For them to be detected, you would have to remove them, commit, put them back, and commit again, or [run the action manually](#running-the-action-manually).
* Should you change the TODO text, this will currently create a new issue.
* Closing TODOs is still somewhat experimental.
@ -111,7 +109,7 @@ There are additional inputs if you want to be able to assign issues to projects.
* Vue
* YAML
New languages can easily be added to the `syntax.json` file used by the action to identify TODO comments. When adding languages, follow the structure of existing entries, and use the language name defined by GitHub in [`languages.yml`](https://raw.githubusercontent.com/github/linguist/master/lib/linguist/languages.yml). PRs adding new languages are welcome and appreciated. Please add a test for your language in order for your PR to be accepted.
New languages can easily be added to the `syntax.json` file used by the action to identify TODO comments. When adding languages, follow the structure of existing entries, and use the language name defined by GitHub in [`languages.yml`](https://raw.githubusercontent.com/github/linguist/master/lib/linguist/languages.yml). PRs adding new languages are welcome and appreciated. Please add a test for your language in order for your PR to be accepted. See [Contributing](#contributing--issues).
## TODO Options
@ -129,9 +127,9 @@ Comma-separated list of labels to add to the issue. If any of the labels do not
Milestone ID to assign to the issue. Only a single milestone can be specified and this must already have been created.
### Other Options
## Other Options
#### Reference
### Reference
As per the [Google Style Guide](https://google.github.io/styleguide/cppguide.html#TODO_Comments), you can provide a reference after the TODO label. This will be included in the issue title for searchability.
@ -143,7 +141,9 @@ As per the [Google Style Guide](https://google.github.io/styleguide/cppguide.htm
Don't include parentheses within the identifier itself.
#### Projects
### Projects
*Please note, the action currently only supports classic user and organisation projects, and not 'new' projects.*
You can assign the created issue to columns within user or organisation projects with some additional setup.
@ -166,15 +166,52 @@ You can assign to multiple projects by using commas, for example: `user projects
You can also specify default projects in the same way by defining `USER_PROJECTS` or `ORG_PROJECTS` in your workflow file. These will be applied automatically to every issue, but will be overrode by any specified within the TODO.
## Running the action manually
There may be circumstances where you want the action to run for a particular commit(s) already pushed.
You can run the action manually by adding support for the `workflow_dispatch` event to your workflow file:
```yaml
name: "Run TODO to Issue"
on:
push:
workflow_dispatch:
inputs:
MANUAL_COMMIT_REF:
description: "The SHA of the commit to get the diff for"
required: true
MANUAL_BASE_REF:
description: "By default, the commit entered above is compared to the one directly before it; to go back further, enter an earlier SHA here"
required: false
jobs:
build:
runs-on: "ubuntu-latest"
steps:
- uses: "actions/checkout@v3"
- name: "TODO to Issue"
uses: "alstr/todo-to-issue-action@master"
env:
MANUAL_COMMIT_REF:
${{ inputs.MANUAL_COMMIT_REF }}
MANUAL_BASE_REF:
${{ inputs.MANUAL_BASE_REF }}
```
Head to the Actions section of your repo, select the workflow and then 'Run workflow'.
You can run the workflow for a single commit, whereby the action will compare the commit to the one directly before it. Enter the commit SHA in the first box.
You can also compare a broader range of commits. In this case, also enter the 'from'/base commit SHA in the second box.
## Troubleshooting
### No issues have been created
Make sure your file language is in `syntax.json`. Also, the action will not recognise existing TODOs that have already been pushed.
If a similar TODO appears in the diff as both an addition and deletion, it is assumed to have been moved, so is ignored.
In case, your workflow is executed but no issue is generated, check if you have given permissions to Workflows. Go to your GitHub Project, Settings->Actions(General)->Workflow permissions and Enable "Read and write permissions".
* Make sure your file language is in `syntax.json`.
* The action will not recognise existing TODOs that have already been pushed, unless you [run the action manually](#running-the-action-manually).
* If a similar TODO appears in the diff as both an addition and deletion, it is assumed to have been moved, so is ignored.
* If your workflow is executed but no issue is generated, check your repo permissions by navigating to `Settings -> Actions (General) -> Workflow permissions` and enable "Read and write permissions".
### Multiple issues have been created
@ -184,6 +221,8 @@ Issues are created whenever the action runs and finds a newly added TODO in the
If you do encounter any problems, please file an issue or submit a PR. Everyone is welcome and encouraged to contribute.
**If submitting a request to add a new language, please ensure you add the appropriate tests covering your language. In the interests of stability, PRs without tests cannot be considered.**
## Running tests locally
To run the tests locally, simply run the following in the main repo: