Skip to content

feat: pulse CI failure pattern detection — identify systemic workflow bugs #2979

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
marcusquinn merged 4 commits into from
Mar 6, 2026
Merged

feat: pulse CI failure pattern detection — identify systemic workflow bugs #2979

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
9557d5c
feat: add systemic CI failure pattern detection to pulse
marcusquinn Mar 6, 2026
9c7c656
chore: re-trigger CI after review-bot-gate fix (GH#3007)
marcusquinn Mar 6, 2026
59cfedc
chore: re-trigger CI (CodeRabbit status now available)
marcusquinn Mar 6, 2026
087535d
chore: re-trigger CI (CodeRabbit status confirmed on previous commit)
marcusquinn Mar 6, 2026
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
2 changes: 1 addition & 1 deletion .agents/scripts/commands/pulse.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -122,7 +122,7 @@ Then skip to the next PR. The next pulse cycle will retry the permission check
- `SKIP` means the PR has a `skip-review-gate` label — it bypasses the bot gate only, NOT the review count requirement.
- Skip the PR when the formal review count is 0, regardless of bot gate status.
- **Green CI + zero reviews** → skip this cycle. Zero reviews means "not yet reviewed", NOT "clean to merge". Review bots typically post within 2-5 minutes. The next pulse will pick it up once a review exists.
- **Failing CI or changes requested** → dispatch a worker to fix it (counts against worker slots)
- **Failing CI or changes requested** → before dispatching a fix worker, check whether this is a systemic failure (see "CI failure pattern detection" below). If systemic, skip the per-PR dispatch — the workflow-level issue covers it. If per-PR, dispatch a worker to fix it (counts against worker slots).

**For all PRs (regardless of author):**

Expand Down