todo-to-issue-action
todo-to-issue-action copied to clipboard
alstr
Action that converts TODO comments to GitHub issues on push.
Hi, I wonder if TODOs with explicitly written issue numbers are supported? For example, let's imagine I have an _Issue 321: "Fix config loading"_ and then I want to have...
Comments are defined like this: ``` .. _This: is a comment! .. [and] this! .. this:: too! .. |even| this:: ! ``` Additionally, support for https://www.sphinx-doc.org/en/master/usage/extensions/todo.html would be awesome ```...
Javadoc comment format for java language has the following format ````java /** * This is the user. * @author someone * @since 0.0.0 */ public class User { } ```
How to force developers to use such a format of TODO items using indentation and expected tags like *labels*, *assignees*, etc.: ```python # TODO Come up with a more imaginative...
Right now I can do `uses: alstr/[email protected]`, but what if `v4.6.3` has a bug, and a newer version called `v4.5.4` fixes the bug? It would be convenient if I could...
I added this action to my repository which has existing `TODO` comments. Because those files weren't diff, it did not create any issues from those `TODO`s. It would be nice...
it would be cool if instead of just closing issues once a PR is merged, it could automatically add the issues that will be closed to the Linked issues of...
https://github.com/alstr/todo-to-issue-action/blob/ade69c5806026ba676eedb1ba3dea412db329f41/main.py#L265-L267 Was wondering if anyone is working on this? How useful is this to anyone else using this action?
I just had an idea how to handle renames: If there is a TODO **removed and added** in the same line of the file, it should be renamed in the...
If a comment spans multiple lines, extend the link in the issue accordingly. It should end in Lxxx-Lyyy. Should be easy to add by calculating the number of lines and...
