Add GITHUB_TOKEN environment variable to MCP server installation in copilot setup workflow #37904
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.
Description
This PR adds the
GITHUB_TOKEN
environment variable to the MCP server installation step in the copilot setup workflow. This enables authenticated GitHub API requests when downloading releases, preventing rate limiting issues and improving installation reliability.Changes
Modified
.github/workflows/copilot-setup-steps.yml
to setGITHUB_TOKEN
from secrets in the "Install azsdk mcp server" step:Why This Change Is Needed
The PowerShell installation script
eng/common/scripts/Helpers/AzSdkTool-Helpers.ps1
already contains logic to check for theGITHUB_TOKEN
environment variable (line 126) to authenticate GitHub API requests. However, the workflow was not providing this token, causing the script to fall back to unauthenticated requests which are subject to strict rate limits.Benefits
GITHUB_TOKEN
(e.g.,summarize-impact.yaml
)Testing
Original prompt
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.