[aw] PR Documentation Check reported incomplete result

[aspire-repo-bot]

Workflow Failure

Workflow: PR Documentation Check
Branch: ellahathaway/vscode-aspire-panel-upgrade-cli-prompt
Run: https://github.com/microsoft/aspire/actions/runs/27861176200

Warning

Task Could Not Be Completed: The agent reported that the task could not be performed due to an infrastructure or tool failure.

Reasons:

• create_pull_request failed 3 times with "ERR_SYSTEM: fatal: Needed a single revision" — the bundle transport cannot pin the source branch because the base commit (ff5fe72) is a grafted shallow-clone entry for release/13.5 on microsoft/aspire.dev, preventing bundle range computation. Approaches tried: (1) branch docs/18358-vscode-panel-error-messages, (2) branch pr18358-vscode-panel-errors with simpler name — same error each time. The docs change (new Troubleshooting section in get-started/aspire-vscode-extension.mdx) is committed locally on branch pr18358-vscode-panel-errors and ready to push; the infrastructure shallow clone prevents the safe-outputs push mechanism from working.

  Change summary

PR #18358 ("Stop false Aspire CLI upgrade warning in VS Code Extension") by @ellahathaway, merged 2026-06-20, fixes a bug where the Aspire panel showed an "Update Aspire CLI" prompt for any AppHost fetch error. The fix separates compatibility errors from generic runtime errors using a new aspire.fetchAppHostsCompatibilityError VS Code context key.

Docs change prepared (but not pushed)

File: src/frontend/src/content/docs/get-started/aspire-vscode-extension.mdx
Branch: pr18358-vscode-panel-errors (based on release/13.5)
Target base: release/13.5

Added a "Troubleshooting the Aspire panel" section documenting:

• Compatibility error message → update CLI and AppHost package
• Generic load-error message → check Aspire Extension output channel

Infrastructure failure

All three create_pull_request attempts returned:

Failed to pin branch '...' before bundle generation: ERR_SYSTEM: fatal: Needed a single revision

The release/13.5 tip (ff5fe72) is a grafted commit in this shallow clone. The bundle transport mechanism requires a non-grafted history to generate the range diff for push. Without git fetch --unshallow (unavailable; credentials removed post-checkout), the push cannot proceed.

This is a structured incompletion signal (report_incomplete), not a real task outcome. Any other safe outputs emitted alongside this signal (e.g., comments) describe the failure state, not a completed review or action.

Action Required

Assign this issue to an agent to debug and fix the issue.

Debug with any coding agent

Use this prompt with any coding agent (GitHub Copilot, Claude, Gemini, etc.):

Debug the agentic workflow failure using https://raw.githubusercontent.com/github/gh-aw/main/debug.md

The failed workflow run is at https://github.com/microsoft/aspire/actions/runs/27861176200

Manually invoke the agent

Debug this workflow failure using your favorite Agent CLI and the agentic-workflows prompt.

• Start your agent
• Load the agentic-workflows skill from .github/skills/agentic-workflows/SKILL.md or https://github.com/github/gh-aw/blob/main/.github/skills/agentic-workflows/SKILL.md
• Type debug the agentic workflow pr-docs-check failure in https://github.com/microsoft/aspire/actions/runs/27861176200

Tip

Stop reporting this workflow as a failure

To stop a workflow from creating failure issues, set report-failure-as-issue: false in its frontmatter:

safe-outputs:
  report-failure-as-issue: false

Generated from PR Documentation Check · 793.5 AIC · ◷

• expires on Jun 27, 2026, 5:26 AM UTC

[radical]

Duplicate of #18319 — same pr-docs-check branch-pinning failure (create_pull_request cannot pin the source branch because the base commit is a grafted shallow-clone entry for release/13.5 on microsoft/aspire.dev). That bug already has a fix in flight (#18320), so closing this as a duplicate to keep a single open tracker. Reopen if the failure recurs after #18320 merges.