alstr / todo-to-issue-action

Action that converts TODO comments to GitHub issues on push.
MIT License
603 stars 115 forks source link

"Project does not exist, skipping" when attempting to assign an issue to a project #152

Closed devin-helio closed 1 year ago

devin-helio commented 1 year ago

Hello,

When adding the org information to a TODO, the action tells me it can't find the project. Here's what I've tried:

// by project id
// TODO: test2
//  org projects: orgname/1/Backlog
// by project name
// TODO: test2
//  org projects: orgname/project name/Backlog

Example response/output from the workflow run:

Processing issue 1 of 2
Adding issue to org project 1 of 1
Project does not exist, skipping
Issue created
Processing issue 2 of 2
Issue closed

action configuration:

    steps:
      # ...
      - name: "TODO to Issue"
        uses: "alstr/todo-to-issue-action@v4.10.1"
        id: "todo"
        with:
          PROJECTS_SECRET: ${{ secrets.PROJECTS_SECRET }}

My PAT has both repo and workflow access granted to it. The project is private so I'm not sure how that factors in to things, but I'm not sure what else to try at this point. Thank you in advance.

alstr commented 1 year ago

Hey there, thanks for asking. Everything looks correct there at first glance (except for the project ID variant, that won't work).

This message is basically saying that the response from the GitHub API call to retrieve the list of org projects doesn't contain the one you specified. Most obvious thing to check would be that the org name is correct. Also, is it an "old" style org project (not a new or repo-level one), and are you the project owner? My guess would be that this project is not being found when it's looking for it, either because it just doesn't exist where it's looking or because of some permissions problem.

In theory it should work, but I don't think much testing has been done with org projects, especially since GitHub has launched the new style projects. I'm hoping to redo it all at some point. There's #149 to merge as well in the time being.

devin-helio commented 1 year ago

Okay, thanks for looking into this. I'm assuming it's a new style project because it was just created. I am indeed an owner and I've checked and re-checked the org-name and project name several times but given it's a new style project I think the rest is moot.

I'll keep an eye on this to see if/when new projects are supported. Thanks again.

alstr commented 1 year ago

Thanks for the update; sorry I can't help in your case. Once the GitHub API supports "new" projects, I can have a look at updating the functionality. Until then it's a waiting game.