Disable no-op run reporting for Duplicate Surfacing workflow - #6408
Merged
denelon merged 1 commit intoJul 29, 2026
Merged
Conversation
The agentic Duplicate Surfacing workflow enabled gh-aw's default no-op reporting, which logs every run that finds no duplicate to an auto-created '[aw] No-Op Runs' tracking issue. On winget-cli most new issues have no duplicate, so this produces near-constant noise and contradicts the workflow's detect-only, stay-silent-unless-a-duplicate-is-found design. Set safe-outputs.noop.report-as-issue: false and recompiled the lock. Reported by Trenly on microsoft#6406. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 3701d64a-96ba-42f1-be59-b4e7d2a2820a
denelon
marked this pull request as ready for review
July 29, 2026 18:04
JohnMcPMS
approved these changes
Jul 29, 2026
This was referenced Jul 29, 2026
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
2 participants
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.
📖 Description
The agentic Duplicate Surfacing workflow (added in #6399 / #6400) inherited gh-aw's default no-op reporting. When a run finds no likely duplicate — the common case for most newly opened issues — gh-aw logs the run to an auto-created "[aw] No-Op Runs" tracking issue (#6406), adding a comment per run.
On a high-volume repo like winget-cli this produces near-constant noise and contradicts the workflow's intended design: detect-only, and stay silent unless a likely duplicate is found.
This PR sets
safe-outputs.noop.report-as-issue: falsein the workflow frontmatter and recompiles the lock. The change is config-only — the detect → label (Possible-Duplicate) → comment behavior is unchanged; only the no-op issue/comment reporting is turned off.Reported by @Trenly on #6406.
Authored with GitHub Copilot assistance.
🔗 References
🔍 Validation
gh aw compile duplicate-surfacing→ 0 errors, 0 warnings.noop.report-as-issueandGH_AW_NOOP_REPORT_AS_ISSUEfliptrue→falsein the three generated config sites, plus the frontmatter hash. No job structure, permissions, or action pins changed.✅ Checklist
📋 Issue Type
Microsoft Reviewers: Open in CodeFlow