fix: grant copilot-requests: write for gh-aw copilot engine auth - #8
Merged
Conversation
…cate The compiled workflows failed at runtime: "Error: None of the following secrets are set: COPILOT_GITHUB_TOKEN". Per gh-aw's own failure guidance, adding copilot-requests: write lets the built-in GITHUB_TOKEN drive Copilot inference via the repo's Copilot subscription, avoiding the need for a separate PAT secret.
This was referenced Sep 8, 2026
Closed
Closed
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
1 participant
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 live test of #6 (draft-post) failed at the activation gate:
Per gh-aw's own failure message, adds
copilot-requests: writeto bothworkflows' top-level permissions so the built-in
GITHUB_TOKENcan driveCopilot inference via your Copilot subscription, instead of needing a
separate PAT stored as a secret.