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.
Simply add a comment starting with TODO, followed by a colon and/or space. Here's an example for Python:
def hello_world():
# TODO Come up with a more imaginative greeting
print('Hello world!')Multiline TODOs are supported, and a range of options can be provided to apply to the new issue:
def hello_world():
# TODO Come up with a more imaginative greeting
# Everyone uses hello world and it's boring.
# labels: enhancement, help wanted
# assignees: alstr, bouteillerAlan, hbjydev
# milestone: 1
print('Hello world!')Create a workflow.yml file in your .github/workflows directory like:
name: "Workflow"
on: ["push"]
jobs:
build:
runs-on: "ubuntu-latest"
steps:
- uses: "actions/checkout@master"
- name: "TODO to Issue"
uses: "alstr/todo-to-issue-action@v4.3"
id: "todo"See Github's workflow syntax for further details on this file.
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. |
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.
- 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.
- Should you change the TODO text, this will currently create a new issue.
- Closing TODOs is still somewhat experimental.
- AutoHotkey
- C
- C++
- C#
- CSS
- Dart
- Elixir
- Handlebars
- HTML
- Java
- JavaScript
- Julia
- Kotlin
- Less
- Markdown
- Objective-C
- Org Mode
- PHP
- Python
- Ruby
- Sass
- Scala
- Shell
- SQL
- Swift
- TeX
- TSX
- TypeScript
- 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. PRs adding new languages are welcome and appreciated.
Unless specified otherwise, options should be on their own line, below the initial TODO declaration.
Comma-separated list of usernames to assign to the issue.
Comma-separated list of labels to add to the issue. If any of the labels do not already exist, they will be created. The todo label is automatically added to issues to help the action efficiently retrieve them in the future.
Milestone ID to assign to the issue. Only a single milestone can be specified and this must already have been created.
As per the Google Style Guide, you can provide a reference after the TODO label. This will be included in the issue title for searchability.
def hello_world():
# TODO(alstr) Come up with a more imaginative greeting
print('Hello world!')Don't include parentheses within the identifier itself.
You can assign the created issue to columns within user or organisation projects with some additional setup.
The action cannot access your projects by default. To enable access, you must create an encrypted secret in your repo settings, with the value set to a valid Personal Access Token. Then, assign the secret in the workflow file like PROJECTS_SECRET: ${{ secrets.PROJECTS_SECRET }}. Do not enter the raw secret.
To assign to a user project, use the user projects: prefix. To assign to an organisation project, use org projects: prefix.
The syntax is <user or org name>/project name/column name. All three must be provided.
def hello_world():
# TODO Come up with a more imaginative greeting
# Everyone uses hello world and it's boring.
# user projects: alstr/Test User Project/To Do
# org projects: alstrorg/Test Org Project/To Do
print('Hello world!')You can assign to multiple projects by using commas, for example: user projects: alstr/Test User Project 1/To Do, alstr/Test User Project 2/Tasks.
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.
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.
Issues are created whenever the action runs and finds a newly added TODO in the diff. Rebasing may cause a TODO to show up in a diff multiple times. This is an acknowledged issue, but you may have some luck by adjusting your workflow file.
If you do encounter any problems, please file an issue or submit a PR. Everyone is welcome and encouraged to contribute.
The action was developed for the GitHub Hackathon. Whilst every effort is made to ensure it works, it comes with no guarantee.
Thanks to Jacob Tomlinson for his handy overview of GitHub Actions.
Thanks to GitHub's linguist repo for the languages.yml file used by the app to look up file extensions and determine the correct highlighting to apply to code snippets.
Thanks to all those who have contributed to the further development of this action.