Don't open issues on agentic workflow no-op runs#688
Conversation
Set `safe-outputs.noop.report-as-issue: false` for all agentic workflows (check-python-versions, extension-template-sync, issue-triage) so a no-op run logs instead of creating a GitHub issue. Recompiled lock files (GH_AW_NOOP_REPORT_AS_ISSUE flips to 'false'); no other behavior changes. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
| @@ -27,6 +27,7 @@ safe-outputs: | |||
| draft: true | |||
| noop: | |||
There was a problem hiding this comment.
📍 .github/workflows/check-python-versions.md:27
The Advocate flagged a genuine trade-off here: this workflow's Step 1 instructs the agent to "call the noop safe output with the error and stop" on a fetch/parse failure. Previously such a failure surfaced as a visible issue; with report-as-issue: false it now only logs in a run that fires once a year, so a real failure could go unnoticed until the next annual run. For the other two workflows no-op purely means "nothing to do" and suppression is clearly correct, but here the no-op channel doubled as an error alarm. Consider a conscious decision — e.g. keep issue-reporting where no-op encodes an error, or add a separate failure notification. Non-blocking.
[verified]
rchiodo
left a comment
rchiodo
left a comment
There was a problem hiding this comment.
Approved via Review Center.
2 participants
Summary
Agentic workflows (gh-aw) currently open a GitHub issue whenever a run is a no-op (the agent has nothing to do). This adds
safe-outputs.noop.report-as-issue: falseto all three agentic workflows so a no-op is logged instead of filing an issue.Changes
For
check-python-versions,extension-template-sync, andissue-triage:.md: addnoop.report-as-issue: falseundersafe-outputs..lock.yml:GH_AW_NOOP_REPORT_AS_ISSUEflips'true'→'false'(+ frontmatter hash). No other behavior changes.Generated with
gh aw compile(v0.51.6); lock diffs kept minimal.