Disable no-op issue reporting for CI Failure Doctor by dondonz · Pull Request #4346 · graphql-java/graphql-java · GitHub
Skip to content

Disable no-op issue reporting for CI Failure Doctor#4346

Merged
dondonz merged 1 commit intomasterfrom
dondonz/github-agentic-workflows
Mar 22, 2026
Merged

Disable no-op issue reporting for CI Failure Doctor#4346
dondonz merged 1 commit intomasterfrom
dondonz/github-agentic-workflows

Conversation

@dondonz
Copy link
Copy Markdown
Member

@dondonz dondonz commented Mar 21, 2026

Summary

  • Adds noop: report-as-issue: false to CI Failure Doctor frontmatter to stop coverage-only no-op runs from spamming issue [aw] No-Op Runs #4342 with "no action required" comments
  • Lock file recompiled via gh aw compile

Closes #4342

Test plan

  • Verify next coverage-only CI failure does not post a no-op comment to [aw] No-Op Runs #4342
  • Verify real CI failures still create issues and comments as expected

🤖 Generated with Claude Code

Coverage-only failures trigger CI Failure Doctor but result in no-op
runs that spam issue #4342 with "no action required" comments. Setting
report-as-issue: false for noop outputs suppresses this noise.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@github-actions
Copy link
Copy Markdown
Contributor

@dondonz dondonz merged commit ee007b0 into master Mar 22, 2026
11 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[aw] No-Op Runs

1 participant