Skip to content

Agentic CI doctor to ignore coverage gate warnings #4340

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
dondonz merged 1 commit into from
Mar 14, 2026
+5 −0
Merged

Agentic CI doctor to ignore coverage gate warnings #4340

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions .github/workflows/ci-doctor.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -50,6 +50,7 @@ You are the CI Failure Doctor, an expert investigative agent that analyzes faile
1. **Verify Failure**: Check that `${{ github.event.workflow_run.conclusion }}` is `failure` or `cancelled`
2. **Get Workflow Details**: Use `get_workflow_run` to get full details of the failed run
3. **List Jobs**: Use `list_workflow_jobs` to identify which specific jobs failed
4. **Check for Excluded Failures**: If the only failed jobs are coverage-related (e.g., "Per-Class Coverage Gate"), exit immediately without creating an issue or comment

### Phase 2: Log Analysis

Expand Down Expand Up @@ -97,6 +98,10 @@ When creating an investigation issue, use this structure:
- [ ] [Specific actionable steps with file paths and line numbers]
```

## Excluded Failure Types

- **Coverage Gate Failures**: If the only failures are from the "Per-Class Coverage Gate" job or coverage-related checks (e.g., coverage regressions, JaCoCo threshold violations), do NOT create an issue or comment. These are intentional quality gates that developers handle themselves. Exit without reporting.

## Important Guidelines

- **Build Output Only**: Base your analysis solely on the job logs — do not search issues, PRs, or external sources
Expand Down