Disable failure-as-issue for Sub-Issue Closer workflow#9000
Merged
Evangelink merged 1 commit intoJun 10, 2026
Merged
Conversation
The Sub-Issue Closer is a scheduled workflow that occasionally fails due to transient infrastructure issues (e.g. Docker registry timeouts when pulling MCP container images such as `node:lts-alpine`). Those infra failures filed noisy `[aw] Sub-Issue Closer failed` tracking issues that are not actionable code defects. Add `safe-outputs.report-failure-as-issue: false` so transient failures no longer file tracking issues, matching the pattern already used in `adhoc-qa.md`, `build-failure-analysis.md`, and `build-failure-analysis-command.md`. Fixes microsoft#8988. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Contributor
There was a problem hiding this comment.
Pull request overview
Disables the agentic-workflow “failure-as-issue” behavior for the scheduled Sub-Issue Closer workflow, preventing noisy tracking issues when the run fails due to transient infrastructure problems (e.g., container pull timeouts) rather than a workflow defect.
Changes:
- Set
safe-outputs.report-failure-as-issue: falsein.github/workflows/sub-issue-closer.md. - Regenerated
.github/workflows/sub-issue-closer.lock.ymlso the compiled workflow emitsGH_AW_FAILURE_REPORT_AS_ISSUE: "false".
Show a summary per file
| File | Description |
|---|---|
| .github/workflows/sub-issue-closer.md | Adds report-failure-as-issue: false in safe-outputs (consistent with other unattended/scheduled workflows). |
| .github/workflows/sub-issue-closer.lock.yml | Regenerated lockfile reflecting the new frontmatter hash and GH_AW_FAILURE_REPORT_AS_ISSUE: "false" in the compiled workflow. |
Copilot's findings
- Files reviewed: 2/2 changed files
- Comments generated: 0
Evangelink
deleted the
dev/amauryleve/fix-8988-sub-issue-closer-no-failure-issue
branch
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Closes #8988.
Problem
The Sub-Issue Closer is an unattended daily scheduled workflow. Run #27256848324 failed with a transient Docker registry timeout while pulling the
node:lts-alpineMCP container image:That is not a code defect, but the workflow's default
report-failure-as-issuebehaviour filed a noisy[aw] Sub-Issue Closer failedtracking issue regardless.Fix
Set
safe-outputs.report-failure-as-issue: falseinsub-issue-closer.md(and regeneratesub-issue-closer.lock.ymlviagh aw compile --strict).This matches the existing pattern already used for similar scheduled / unattended agentic workflows:
.github/workflows/adhoc-qa.md.github/workflows/build-failure-analysis.md.github/workflows/build-failure-analysis-command.mdThe agentic-workflow tip embedded in #8988 explicitly recommends this exact remediation.
Verification
gh aw compile sub-issue-closer --strict→ ✓ 0 errors / 0 warnings.grep GH_AW_FAILURE_REPORT_AS_ISSUE sub-issue-closer.lock.ymlshows the env var is now emitted as"false".