Fix issue analyzer workflow: add projects: write permission#2843
Merged
Fix issue analyzer workflow: add projects: write permission#2843
projects: write permission#2843Conversation
…TOKEN The workflow was failing with "Could not resolve to a ProjectV2 with the number 7" because GITHUB_TOKEN lacked the `projects: write` permission needed to access GitHub Projects V2 (org-level) via the GraphQL API. Added `projects: write` to both the top-level and job-level permissions so that the GITHUB_TOKEN has the necessary scope to query and update the org project. Co-authored-by: einari <134365+einari@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Fix issue analyzer workflow functionality
Fix issue analyzer workflow: add Mar 14, 2026
projects: write permission
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The issue analyzer workflow was failing because
GITHUB_TOKENlacked theprojects: writescope required to access GitHub Projects V2 at the org level via GraphQL. GitHub's API returns "Could not resolve to a ProjectV2" (rather than a 403) when the token lacks project scope — making it look like the project doesn't exist.Fixed
projects: writeto both the top-level and job-level permissions inissue-analysis.ymlsoGITHUB_TOKENcan query and updatehttps://github.com/orgs/Cratis/projects/7💬 Send tasks to Copilot coding agent from Slack and Teams to turn conversations into code. Copilot posts an update in your thread when it's finished.