[docs] Update documentation for features from 2026-07-08#44275
Merged
pelikhan merged 1 commit intoJul 8, 2026
Conversation
pelikhan
deleted the
docs/update-auth-token-guidance-2026-07-08-72ceb55f88a19fc9
branch
July 8, 2026 11:35
Contributor
Author
|
🎉 This pull request is included in a new release. Release: |
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.
Summary
Documentation update clarifying that gh-aw validates token type at runtime and intentionally rejects OAuth user tokens (
gho_...) forCOPILOT_GITHUB_TOKENandGH_AW_GITHUB_TOKEN.Changes
docs/src/content/docs/reference/auth.mdx(+4 lines)COPILOT_GITHUB_TOKENsection: documents runtime token-type validation during activation. If eitherCOPILOT_GITHUB_TOKENorGH_AW_GITHUB_TOKENstarts with the OAuth token prefix (gho_), the workflow fails early with guidance to replace it with a fine-grained PAT. Explains that OAuth user tokens are intentionally rejected because they are broad user-session credentials and cannot be scoped appropriately for automation.GH_AW_GITHUB_TOKENsection: reinforces that this secret must be a PAT rather than an OAuth user token. Documents that gh-aw now fails early during activation when either secret uses agho_...token, with remediation pointing to creating a fine-grained PAT.Behaviour Documented
COPILOT_GITHUB_TOKENgho_GH_AW_GITHUB_TOKENgho_Commits
a3e537bdocs: clarify PAT-only token validation