add-to-project: Could not resolve to a node with the global id of '******'

I have a github workflow using this action that adds all issues with a bug label to my project board. I’ve configured the workflow in two repos with the same github token available to both (via organization secrets).

In one repo the action is working correctly. In another I am seeing this error:

Could not resolve to a node with the global id of '******'

I’ve hidden the id value from the error cause I don’t know if that’s sensitive or not. The id is meaningless to me and looks like some opaque identifier.

About this issue

Original URL
State: closed
Created 2 years ago
Reactions: 9
Comments: 20 (3 by maintainers)

Most upvoted comments

For those of you still having this issue, I added the repo scope and it works now for us

fidou on Nov 23, 2022

👋 We are currently working on deploying some internal security policy updates that we think might be related to this issue. We are tracking this issue in our internal backlog and we’ll let you know when we have any updates.

In the meantime, for anyone who has been experiencing this issue (@defunctzombie @jlind23 @momobel), could you provide more information on your setup? The following would be helpful:

What type of personal access token you have configured
What permissions the access token has available to it
Is a GitHub App token being used?
Any other info related to the integration: repository scope, org scope, etc.

camchenry on Sep 1, 2022

We have a public board under an organization and a private repository as well under the same organization. The script was not working and failed with the error mentioned above. Initially, I did not check the repo:invite scope, - I though it is unrelated but actually that was the problem. After I checkmarked that it started to work.

molnard on May 25, 2023

Came across this during my googling of a similar issue I faced. The GH GraphQL API mutation called updateProjectV2DraftIssue wasn’t able to resolve a draft issue id that I knew existed. Turns out this hasn’t been fully rolled out yet and my query returning the issue IDs was returning old format IDs. Adding X-Github-Next-Global-ID: 1 header to the query returned the correct IDs and those worked with the mutations as well.

Hope this helps!

kurkel on Jan 20, 2023