Fix GitHub Remote MCP auth test returning empty gh api output #10917
+61
−27
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.
Remote MCP server initialization fails with "invalid session" (400), but agent silently falls back to
gh apiwhich returns empty output with exit 0, causing false positive test passes.Changes
Workflow Instructions (
.github/workflows/github-remote-mcp-auth-test.md)gh apicommand - test must use MCP toolsContext
MCP Gateway continues startup even when GitHub backend fails to initialize:
Agent sees no GitHub tools available, falls back to
gh api /repos/.../issues, gets empty output. Workflow succeeds but creates discussion about auth failure.This fix prevents the fallback behavior. Follow-up work needed: MCP Gateway should fail startup when critical backends fail.
Original prompt
💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.