Set up for simple use.

[sitenzo]

Hi All,

I have created a workflow todo.yml workflow

name: "Run TODO to Issue"
on: [ "push" ]
jobs:
  build:
    runs-on: "ubuntu-latest"
    steps:
      - uses: "actions/checkout@v3"
      - name: "TODO to Issue"
        uses: "alstr/todo-to-issue-action@v4"
        id: "todo"

After this i created a todo in my project file (.php)

        // todo: Send dynamic Welcome Mail to Users
        // This needs to be dynamic, admins need to manage welcome mail text and lay-out.

The action is running but there is no issue created.
Even if i try different formats of todo like

// @todo test1
// todo: test2
/*
 * todo: test3
 */ 

How can i investigate this further and so it will create issues for me on Github?

This is a public repo https://github.com/sitenzo/test-todo

I think i need to change some configuration but don't know witch one for this to work.

Thanks for the help

[alstr]

Looking at your action log, the issues were only picked up on the last run, but then the API call to GitHub failed so the issues could not be created.

I've run a few tests and the API seems to be working for me.

Can you try the following:

• Use TODO in uppercase (lowercase should technically work but I've noticed that it doesn't... but your last action run seemed to pick them up, so I'm confused)
• Make sure a colon follows afterwards with no space before it
• Add a line of actual code below each TODO (again should work without)
• Use v4 which targets the latest v4 release

[sitenzo]

Hi @alstr

After some testing i think i get it working.

if i use // TODO: it works
it won't work on

/*
 * TODO: 
 */

Also, for the issue to be created i needed to change some permission (Maybe did not read the docs properly for this setting)

From : Read repository contents and packages permissions
To : Read and write permissions

[alstr]

Hi @sitenzo, thanks for the update.

I'm glad you got it (partly) working. I thought it might be related to permissions.

Lowecase todo should hopefully work going forward.

Regarding the second example you highlighted, at the moment the app looks for the TODO label on the same line that the comment starts, so this does not work currently but might change in future.