Skip to content

fix(workflows): silence issue-triage-agent no-op runs in #63#119

Merged
arnaudlh merged 1 commit into
mainfrom
fix/issue-triage-agent-noop-reporting
May 25, 2026
Merged

fix(workflows): silence issue-triage-agent no-op runs in #63#119
arnaudlh merged 1 commit into
mainfrom
fix/issue-triage-agent-noop-reporting

Conversation

@arnaudlh

Copy link
Copy Markdown
Member

Summary

The Issue Triage Agent runs on a weekday cron and finds nothing to triage on most invocations (all open issues are already labeled or assigned). Each of those runs currently posts a no action needed comment to the [aw] No-Op Runs tracking issue (#63), which has produced a steady stream of noise.

This PR adds the documented opt-out for that behavior.

Change

safe-outputs:
  add-labels:
    allowed: [bug, feature, ...]
  add-comment: {}
  noop:
    report-as-issue: false   # ← new

Recompiled the lock file with the repo-pinned gh-aw v0.72.1 (gh aw compile). The compiler also pinned github/gh-aw-actions/setup@v0.72.1 by SHA in .github/aw/actions-lock.json (it was previously using the bare tag), which is a small hardening side effect within the same version.

Verification

  • compiler_version in the lock file remains at v0.72.1.
  • GH_AW_NOOP_REPORT_AS_ISSUE: "false" is present in the compiled lock yml.
  • The handler config JSON contains \"noop\":{\"max\":1,\"report-as-issue\":\"false\"}.

Closes

Fixes #63

Add safe-outputs.noop.report-as-issue: false to the issue triage agent
workflow so its weekday no-op runs no longer post a comment to
the [aw] No-Op Runs tracking issue (#63). The agent legitimately finds
nothing to triage on most runs; flooding the tracking issue with
'no action needed' comments is noise.

Recompiled the lock file with gh-aw v0.72.1 (matching the repo's pinned
compiler_version), which also pinned github/gh-aw-actions/setup@v0.72.1
by SHA in actions-lock.json.

Fixes #63
@arnaudlh arnaudlh requested a review from sendtoshailesh May 25, 2026 02:53
@sendtoshailesh

Copy link
Copy Markdown
Contributor

✅ Review — LGTM

Verified the 3-file change:

  • issue-triage-agent.md: noop: report-as-issue: false correctly opts out of [aw] No-Op Runs #63 noise
  • issue-triage-agent.lock.yml: recompiled with v0.72.1, config JSON shows "report-as-issue":"false" in both config.json heredoc and GH_AW_SAFE_OUTPUTS_HANDLER_CONFIG env var
  • actions-lock.json: SHA pin for gh-aw-actions/setup@v0.72.1 (bc56a0cad2f450c562810785ef38649c04db812a) — nice hardening side effect

No functional concerns. Ready to merge.

@arnaudlh arnaudlh merged commit dd91efc into main May 25, 2026
5 checks passed
@arnaudlh arnaudlh deleted the fix/issue-triage-agent-noop-reporting branch May 25, 2026 07:38
@arnaudlh arnaudlh added this to the v0.1.0 milestone May 25, 2026
@arnaudlh arnaudlh added the bug Something isn't working label May 25, 2026
@arnaudlh arnaudlh self-assigned this May 25, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[aw] No-Op Runs

2 participants