Fix daily-team-evolution-insights timeout by switching to remote GitHub MCP mode #10553
+125
−37
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 Daily Team Evolution Insights workflow timed out after 45 minutes in all 7 runs. The workflow used
mode: localfor the GitHub MCP server, requiring Docker container download, startup, and inter-process communication overhead.Changes
.github/workflows/daily-team-evolution-insights.md: Changed GitHub MCP mode fromlocaltoremote.github/workflows/daily-team-evolution-insights.lock.yml: Recompiled workflow, removing Docker image download stepTechnical Details
Before: Docker-based MCP server
After: Hosted MCP server
Remote mode connects directly to
https://api.githubcopilot.com/mcp/via HTTPS, eliminating container overhead. Same pattern used by successful workflows likedaily-repo-chronicle.Original prompt
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.