Disable no-op issue reporting for CI Failure Doctor#4346
Merged
Conversation
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>
Contributor
Test ReportTest Results
Code Coverage (Java 25)
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
noop: report-as-issue: falseto CI Failure Doctor frontmatter to stop coverage-only no-op runs from spamming issue [aw] No-Op Runs #4342 with "no action required" commentsgh aw compileCloses #4342
Test plan
🤖 Generated with Claude Code