Problem
The add-community-extension and add-community-preset agentic workflows post no-op comments to the [aw] No-Op Runs tracking issue (#2746) every time they determine an issue isn't a submission for them.
For example, when issue #2744 (an enhancement) was labeled, both workflows ran, correctly determined no action was needed, and then posted comments like:
No action needed: Issue #2744 is not an extension submission (title does not start with [Extension]:, has enhancement label instead of extension-submission label)
These are noise — the workflows are working correctly, but reporting their no-ops clutters the tracking issue.
Fix
Add noop: report-as-issue: false to the safe-outputs frontmatter in both workflow files, as documented in the tracking issue itself:
.github/workflows/add-community-extension.md
.github/workflows/add-community-preset.md
Problem
The
add-community-extensionandadd-community-presetagentic workflows post no-op comments to the [aw] No-Op Runs tracking issue (#2746) every time they determine an issue isn't a submission for them.For example, when issue #2744 (an enhancement) was labeled, both workflows ran, correctly determined no action was needed, and then posted comments like:
These are noise — the workflows are working correctly, but reporting their no-ops clutters the tracking issue.
Fix
Add
noop: report-as-issue: falseto thesafe-outputsfrontmatter in both workflow files, as documented in the tracking issue itself:.github/workflows/add-community-extension.md.github/workflows/add-community-preset.md