Use copilot-requests: write permission instead of PAT for agentic workflows#8717
Merged
Merged
Conversation
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
JeffreyCA
changed the title
copilot-requests: write permission instead of PAT for agentic workflows
JeffreyCA
requested review from
RickWinter,
danieljurek,
tg-msft and
vhvb1989
as code owners
Contributor
There was a problem hiding this comment.
Pull request overview
This PR updates the repo’s agentic GitHub Actions workflows to authenticate Copilot inference using the built-in GitHub Actions token plus the copilot-requests: write permission (instead of relying on a long-lived COPILOT_GITHUB_TOKEN secret), and refreshes the generated gh-aw compiled/maintenance artifacts accordingly.
Changes:
- Add
copilot-requests: writepermissions to agentic workflows and switch Copilot auth to use${{ github.token }}. - Regenerate gh-aw compiled
.lock.ymlworkflows and maintenance workflow to newer gh-aw tooling (v0.79.8). - Update the extension PR labeler workflow prompt to better infer target extension IDs from PR metadata (including registry-only PR titles).
Show a summary per file
| File | Description |
|---|---|
| .github/workflows/update-instructions-from-pr-reviews.md | Adds copilot-requests: write and updates wording around auth requirements. |
| .github/workflows/update-instructions-from-pr-reviews.lock.yml | Regenerated compiled workflow: removes COPILOT_GITHUB_TOKEN secret validation and uses ${{ github.token }} for Copilot auth; updates gh-aw version and related scaffolding. |
| .github/workflows/extension-pr-labeler.md | Adds copilot-requests: write, disables checkout in frontmatter, and expands prompt instructions to use PR metadata. |
| .github/workflows/extension-pr-labeler.lock.yml | Regenerated compiled workflow: removes COPILOT_GITHUB_TOKEN secret validation and uses ${{ github.token }} for Copilot auth; updates gh-aw version and related scaffolding. |
| .github/workflows/agentics-maintenance.yml | Regenerated maintenance workflow to gh-aw v0.79.8. |
| .github/aw/actions-lock.json | Updates pinned gh-aw action entries to v0.79.8. |
Copilot's findings
- Files reviewed: 6/6 changed files
- Comments generated: 1
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
vhvb1989
approved these changes
Jun 19, 2026
Contributor
Author
|
/check-enforcer override |
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.
Fixes #8272
This PR updates the agentic workflows to use the GitHub Actions token for Copilot inference via the
copilot-requests: writepermission instead of requiring a long-livedCOPILOT_GITHUB_TOKENsecret.This is based on updated guidance now that org-wide billing is now supported for agent workflows.
It also refreshes the generated gh-aw lock and maintenance workflows and slightly improves the extension labeler prompt so registry-only PRs can infer the target extension from PR metadata.