Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

main/v0.5.0: Could not resolve to a ProjectV2 with the number #462

Closed
ssbarnea opened this issue Sep 8, 2023 · 4 comments
Closed

main/v0.5.0: Could not resolve to a ProjectV2 with the number #462

ssbarnea opened this issue Sep 8, 2023 · 4 comments

Comments

@ssbarnea
Copy link

ssbarnea commented Sep 8, 2023

Apparently this action does not work and gives and error about failure to find the project.

Could not resolve to a ProjectV2 with the number

I tried to use both latest release @v0.5.0 and @main but the result was the same.

I know that the token is good because it used in another action that is called before this one.

https://github.com/ansible/devtools/actions/runs/6121911508/job/16616619759?pr=132

I might be missing something but I also know that https://github.com/orgs/ansible/projects/86 is a valid project too.

The workflow source is at https://github.com/ansible/devtools/blob/main/.github/workflows/ack.yml#L52-L58

@ssbarnea
Copy link
Author

ssbarnea commented Sep 8, 2023

@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.

@mattcosta7
Copy link
Contributor

@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

@mattcosta7
Copy link
Contributor

mattcosta7 commented Sep 9, 2023

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!)

@ssbarnea
Copy link
Author

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants