Fix upgrade command documentation - clarify repository scope
#11559
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
upgradecommand documentation incorrectly stated it "upgrades the gh-aw extension." The command only upgrades repository files (agent templates, workflows) and validates the extension version—it does not upgrade the extension itself.Changes
Context
The command checks if the extension is current (
ensureLatestExtensionVersion) but prompts users to rungh extension upgrade githubnext/gh-awseparately if outdated. Documentation now matches implementation behavior inpkg/cli/upgrade_command.go.Original prompt
upgradecommand in main CLI documentation #11288✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.