Alastair Mooney
Alastair Mooney
Hey, thanks for the suggestion. I think this is doable. The TODO already accepts a reference parameter, so if the issue number was supplied here, we could find the issue...
From your original post I assumed that you were talking about having already created the issue, then wanting to later link code blocks to that issue, is that correct? So...
Let's say there is an existing issue, say #123. If we were to add a TODO like this: ```python # TODO(123) Refactor this code. ``` This would be added as...
Not at the moment, but this is certainly doable. We can't treat references as assignees by default as the [reference may not always be an assignee](https://google.github.io/styleguide/cppguide.html#TODO_Comments): ``` // TODO([email protected]): Use...
I have thought about doing this and it would definitely be possible. We do for now need to retain the `todo` label as that is what the action uses to...
If you edit the action code to change the label it uses from `todo` to `todos` that would work. If you change the labels manually on the issues then that...
I've just pushed a commit for this functionality. I've not created an actual release for it yet but will do soon. Example usage (add to `workflow.yml`): `IDENTIFIERS: '[{"name": "TODO", "labels":...
Now live in `v4.7`. 😄
Interesting, thanks for the suggestion! It would definitely be good to add this; PR requests are always welcome for new languages, and they're relatively easy to do. This does look...
I've done some experimentation and the challenges to adding this at the moment are: - [x] The lowercase `todo` (added support in latest commit) - [ ] The double colon...