Update Aspire configuration and GitHub Actions workflows#611
Conversation
There was a problem hiding this comment.
Pull request overview
Updates local MCP configuration and GitHub Actions “agentic workflows” tooling to newer gh-aw/AWF versions, and adds an Aspire skill document intended to guide Aspire-related operations in this repo.
Changes:
- Update VS Code MCP config for Aspire and reformat MCP server args blocks.
- Bump gh-aw tooling references across generated workflow lockfiles and the setup workflow.
- Add an Aspire skill markdown document under
.github/skills/aspire/.
Reviewed changes
Copilot reviewed 8 out of 8 changed files in this pull request and generated 3 comments.
Show a summary per file
| File | Description |
|---|---|
| .vscode/mcp.json | Changes how VS Code launches the Aspire MCP server. |
| .github/workflows/repo-assist.lock.yml | Regenerated lockfile with gh-aw v0.65.4 / AWF v0.25.6 and related workflow behavior tweaks. |
| .github/workflows/copilot-setup-steps.yml | Updates the gh-aw setup-cli action/version. |
| .github/workflows/ci-coach.lock.yml | Regenerated lockfile with gh-aw v0.65.4 / AWF v0.25.6. |
| .github/workflows/agentics-maintenance.yml | Regenerated maintenance workflow with updated gh-aw action pins. |
| .github/skills/aspire/SKILL.md | Adds Aspire skill documentation for repo usage. |
| .github/aw/actions-lock.json | Updates pinned gh-aw action SHAs/versions used by workflows. |
| .github/agents/agentic-workflows.agent.md | Updates gh-aw documentation links to v0.65.4. |
| "agent", | ||
| "mcp" |
There was a problem hiding this comment.
The Aspire MCP server is typically started via aspire mcp start (see .agents/skills/aspire/references/mcp-server.md), but this config now invokes aspire agent mcp, which doesn’t appear to be used anywhere else in the repo and is likely an invalid Aspire CLI invocation. Update the args to the supported MCP server start command so VS Code can actually launch the Aspire MCP server.
| "agent", | |
| "mcp" | |
| "mcp", | |
| "start" |
|
|
||
| # Aspire Skill | ||
|
|
||
| This repository uses Aspire to orchestrate its distributed application. Resources are defined in the AppHost project (`apphost.cs` or `apphost.ts`). |
There was a problem hiding this comment.
This claims the AppHost is defined in apphost.cs or apphost.ts, but this repo’s AppHost is src/Garage.AppHost/Program.cs (and there’s no apphost.ts). Please update the file references so the skill points users to the correct entrypoint for editing resources.
| This repository uses Aspire to orchestrate its distributed application. Resources are defined in the AppHost project (`apphost.cs` or `apphost.ts`). | |
| This repository uses Aspire to orchestrate its distributed application. Resources are defined in the AppHost project at `src/Garage.AppHost/Program.cs`. |
| ## Important rules | ||
|
|
||
| - **Always start the app first** (`aspire start`) before making changes to verify the starting state. | ||
| - **To restart, just run `aspire start` again** — it automatically stops the previous instance. NEVER use `aspire stop` then `aspire run`. NEVER use `aspire run` at all. | ||
| - Use `--isolated` when working in a worktree. |
There was a problem hiding this comment.
The “Important rules” section says to never use aspire run and to use aspire start instead, but the repo documentation (e.g., README Quick Start) instructs running the app via aspire run. This inconsistency will mislead users and automation; align the guidance with the repo’s documented run command (or update repo docs consistently if the intended command truly changed).
Enhance the MCP configuration for Aspire and introduce documentation for the Aspire skill. Update GitHub Actions workflows to utilize the latest versions of gh-aw and AWF.