main/v0.5.0: Could not resolve to a ProjectV2 with the number about add-to-project HOT 4 CLOSED

• github-token (required) is a personal access
  token with repo and project scopes.
  See Creating a PAT and adding it to your repository for more details

From the readme, details on that token setup

(Not trying to say read the manual or anything like that - just trying to pass along info quickly while on mobile!)

from add-to-project.

@mattcosta7 I wonder if extra permissions as described on https://docs.github.com/en/actions/using-jobs/assigning-permissions-to-jobs are needed. Still, the only permission that looks related is named repository-projects: read|write|none but to my knowledge these projects are organization level not project level.

Maybe using the implicit token does not allow this and it would only work with a personal token.

from add-to-project.

@mattcosta7 I wonder if extra permissions as described on https://docs.github.com/en/actions/using-jobs/assigning-permissions-to-jobs are needed. Still, the only permission that looks related is named repository-projects: read|write|none but to my knowledge these projects are organization level not project level.

Maybe using the implicit token does not allow this and it would only work with a personal token.

Not near a computer for a bit, but are you using a legacy personal access token, or an action token?

Due to the graphql API backing this if I recall correctly, a personal access token is required

from add-to-project.

Thanks, I can confirm that this is true. I will try to make a PR to mention not to attempt to use non PATs as they will not work.

from add-to-project.