Project not found - Classic project

[BennyDeBock]

So I have been working on creating a workflow to put issues with the good first issue label onto a project board.

I've managed to make this work in an organisation, but it doesn't seem to work when using a public repository with a user project not belonging to an organisation.

https://github.com/BennyDeBock/test-gh-actions/runs/7598890181?check_suite_focus=true

TestBoard (view)

Here is the workflow I'm using.
https://github.com/BennyDeBock/test-gh-actions/blob/main/.github/workflows/project-board.yml

Is there something I'm doing wrong? or somewhere that i'm able to specify the url to the project?
@alex-page

[wnqueiroz]

I have a similar problem here, only in a private context... I'm trying to automate moving issues for a project within an organization. The repository and project are private. What am I doing wrong?

I configured the personal access token scopes in the link:

https://github.com/settings/tokens/new?scopes=repo,write:org&description=PERSONAL_ACCESS_TOKEN

My workflow is set up in an even simpler way:

name: "Foo"

on:
  issues:
    types: [opened]

jobs:
  automate-project-columns:
    runs-on: ubuntu-latest
    steps:
      - uses: alex-page/github-project-automation-plus@v0.8.1
        with:
          project: Foo
          column: Bar
          repo-token: ${{ secrets.PERSONAL_ACCESS_TOKEN }}

I've also enabled SSO on the token...

Screenshot:

[SirMishaa]

Any up ?

We got the same issue for organization, it can't found the project, even with good permission of token.

[BennyDeBock]

@SirMishaa Here you can see a working example I made in the past for the Vapor organisation https://github.com/vapor/ci/blob/main/.github/workflows/issues-to-project-board.yml

[Neehal-ATD]

I have this same problem, and I looked at the action failure logs. Looks like Node.js needs an upgrade, although I'm pretty new to all this so not sure if it's something I can do on my end or the action code's end.

Edit: Just saw this in another thread, I guess it's not really needed that much anymore. #76 (comment)

I'd love to see if it's possible to have our own custom actions though, would really open up quite some new workflow ideas with the custom fields that we can add in projects I believe.

[alex-page]

@Neehal-ATD this action supports NodeJS 16 as a minimum. See the latest commit into the repository.

[Neehal-ATD]

@alex-page Ah ok I think I found the issue; I'd copied the code from the examples you had on the GitHub Marketplace page which had v0.8.1 listed in the syntax, not 0.8.2. 🤦‍♂️I didn't really check if it was the latest version.
You can maybe update the version number on there. Thanks for the response, would not have realized otherwise 😆

[alex-page]

Updated the docs. Thanks Neehal!

[steph-crown]

@wnqueiroz, were you able to get the workflow to work? I get the same error as you did when I tried to use the workflow to move issues to a project in a private organization.

Run alex-page/github-project-automation-plus@v0.8.3
  with:
    project: Test Project
    column: In Progress
    repo-token: ***
    action: update
Error: Could not find the column "In Progress" or project "Test Project"

[OscarCasadoLorenzo]

Same issue as @wnqueiroz and @steph-crown .
@alex-page Do you know how to solve this problem?

[ianwesleyarmstrong]

Also ran into this with v0.8.3.

[alex-page]

I don't know how to solve this problem, I would have to dig through the API docs and replicate it myself. There might be some issues with the logic to find projects as it is meant to check your org and own repos. This might have been changed recently.

[steph-crown]

There is a possibility that this issue arises when using it with Beta projects.

[aptalca]

Is this action working with the new projects? I don't believe they're beta anymore. They are called projects or all new projects and the legacy ones are called classic projects.

Github deprecated the classic projects and it won't let you create new ones unless you already have existing classic projects.

Thanks