From looking at the documentation of that action the workflow as such should be fine as long as the secret you use exists. What I can’t see is the secret: Is it a valid token with the required scopes, and nothing else (no extra spaces, etc.)?

There are not any extra spaces. And the secret is org wide.

image934×99 4.42 KB

actions/add-to-project

Hi @ethan-master-coding
Does your token has with repo , write:org and read:org scopes ?
As mentioned there GitHub - actions/add-to-project: Automate adding issues and pull requests to GitHub projects (beta)

There was no option to give the token perms. The token is from the org and not my user. And the repo does recognize the token.

image1013×244 10.3 KB

Then org owner or admin who provided this token has to add these scopes. It’s no chance to make it work without correct scopes.

I am the owner of the org but I did not see the option to.

image1237×705 15.7 KB

Oh, it needs to be a personal token instead of an org token. Will I need to to change any of the syntax other than needing to change the name of the token? Or for the value of the token the value of my token?

Is yours org Enterprise one?
If you have token on org level you can change scope for existing token

I figured it out thanks @ViacheslavKudinov. And no its a free one.

What was the fix?
I've made a PAT with the correct settings but it returns Bad Credentials