Add diagnostic logging for project resolution failures #13329
Closed
+44
−14
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.
Project 146 resolution fails with "Could not resolve to a ProjectV2" despite correct URL and code logic. Both direct
projectV2(number)and fallbackprojectsV2list queries fail, but insufficient logging prevents identifying whether this is a permission, access, or API issue.Changes
Enhanced diagnostic logging in project resolution:
Files modified:
actions/setup/js/update_project.cjsactions/setup/js/create_project_status_update.cjsExample
Before:
After:
Next workflow run will reveal exact failure point: token permissions, project visibility, or transient API errors.
Original prompt
💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.