Disable no-op runs for duplicate issues workflow #255

Activity

1. github-actions commented on Feb 21, 2026

   

   github-actionsBot

   on Feb 21, 2026 – with GitHub Actions

   Contributor

   More actions

   TL;DR: I recommend implementing this by setting report-as-issue: false for safe-outputs.noop in the duplicate issue detector workflow, because the current config is generating frequent no-op comments into the central no-op issue.

   Recommendation

   Update .github/workflows/gh-aw-duplicate-issue-detector.md so safe-outputs.noop disables issue reporting (report-as-issue: false), then recompile to refresh .lock.yml.

   Findings

   • The duplicate detector currently defines noop with default behavior (no override):
     • .github/workflows/gh-aw-duplicate-issue-detector.md:51-54
       • safe-outputs:
       • noop:
       • add-comment:
   • The compiled workflow confirms noop is active with only max configured:
     • .github/workflows/gh-aw-duplicate-issue-detector.lock.yml:547
       • {"add_comment":{"max":1},"missing_data":{},"missing_tool":{},"noop":{"max":1}}
   • This appears to be causing high-volume no-op reporting in the central tracker issue:
     • #83 ([agentics] No-Op Runs) currently has 55 comments and includes repeated duplicate-detector entries like “No duplicate found for issue Remove git fetch */origin when fixed upstream #225/gh-aw workflows ignoring the triggering comment #226/Allow customizing allowed bot users via a workflow input #227/...”.
     • Sample evidence from fetched comments on #83: comment IDs 3936293288, 3936872597, 3937165178, 3937183216, 3937284187 (all Duplicate Issue Detector no-op messages).
   • Related implementation history:
     • Issue #197 requested the duplicate detector workflow.
     • PR #199 added it and introduced safe-outputs.noop + safe-outputs.add-comment in the source workflow.

   Verification

   I verified current behavior/config locally:

   $ grep -nE "safe-outputs:|noop:|add-comment:" .github/workflows/gh-aw-duplicate-issue-detector.md
   51:safe-outputs:
   52:  noop:
   53:  add-comment:
   
   $ grep -RIn "report-as-issue" .
   # no matches
   

   I also parsed issue #83 comments and confirmed duplicate-detector no-op volume:

   page2: comments=20, duplicate-detector=8
   page3: comments=15, duplicate-detector=15
   sample messages: "No duplicate found for issue #200/#202/#206/#208/#209/#225/#226/#227/..."
   

   Detailed Action Plan

   1. Edit .github/workflows/gh-aw-duplicate-issue-detector.md at safe-outputs (~L51) and change noop to explicit config:
      • from noop:
      • to:

        noop:
          report-as-issue: false

   2. Recompile workflow artifacts (gh aw compile / project compile flow) so .github/workflows/gh-aw-duplicate-issue-detector.lock.yml reflects the new safe-output config.
   3. Validate compiled config in lock file no longer reports noop as issue output.
   4. Keep add-comment unchanged so true duplicate matches still get posted back on the triggering issue.
   5. (Optional follow-up) audit other high-frequency detector/report workflows that intentionally no-op often and apply the same setting where appropriate.

   Related Items

   Type	Link	Relevance
   Issue	#255	Current request
   Issue	#83	Central no-op tracker receiving duplicate-detector no-op comments
   Issue	#197	Original request to add duplicate issue detector
   PR	#199	Added duplicate issue detector workflow
   File	.github/workflows/gh-aw-duplicate-issue-detector.md:51-54	Current safe-outputs.noop definition
   File	.github/workflows/gh-aw-duplicate-issue-detector.lock.yml:547	Compiled safe-output config includes noop
   File	.github/workflows/trigger-duplicate-issue-detector.yml:1-4	Trigger frequency (issues: opened) explains high run volume

   ---

   What is this? | From workflow: Issue Triage Agent

   Give us feedback! React with 🚀 if perfect, 👍 if helpful, 👎 if not. for issue #255
2. strawgate

   assigned

   Copilot

   and

   strawgate

   on Feb 21, 2026
3. strawgate

   closed this as completedin #262on Feb 21, 2026