[aw] PR Documentation Check produced no safe outputs
- Dominant language
- C#
- Stars
- 6.3k
- Forks
- 991
- Avg merge
- 2d 15h
- Merged PRs (30d)
- 196
Description
### Workflow Failure
**Workflow:** [PR Documentation Check](https://github.com/microsoft/aspire/blob/main/.github/workflows/pr-docs-check.md)
**Branch:** dev/karolz/fix-19708
**Run:** https://github.com/microsoft/aspire/actions/runs/33434425767
> [!WARNING]
> **No Safe Outputs Generated**: The agent job succeeded but did not produce any safe outputs.
This typically indicates:
- The safe output server failed to run
- The prompt failed to generate any meaningful result
- The agent should have called `noop` to explicitly indicate no action was taken
### 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/33434425767
````
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
- Type `debug the agentic workflow pr-docs-check failure in https://github.com/microsoft/aspire/actions/runs/33434425767`
> [!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:
> ```yaml
> safe-outputs:
> report-failure-as-issue: false
> ```
>
>
> Generated from [PR Documentation Check](https://github.com/microsoft/aspire/actions/runs/33434425767) · 17.7 AIC · [◷](https://github.com/search?q=repo%3Amicrosoft%2Faspire+is%3Aissue+%22gh-aw-workflow-id%3A+pr-docs-check%22&type=issues)
> - [x] expires on Sep 7, 2026, 8:16 PM UTC
Contributor guide
Research direction
Start with .github/workflows/pr-docs-check.md and inspect the linked failed run to determine why the agent job produced no safe outputs. Trace whether the safe output server or prompt failed, or whether the agent needed to call noop; done means the workflow handles this case correctly and the run no longer reports an unintended failure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100