Repository navigation
Runaway PR candidate(s) detected 2026-09-21 #1878
Description
Runaway PR Detection — 2026-09-21
Repo: petry-projects/.github-private | Open PRs scanned: 15 | Candidates: 6
Runaway PR Candidates
Open PRs exceeding a soft runaway threshold (commits >50, comments >200, automated cycles >10, open >48h with agent churn, or merge-stacked: >50 commits with <20 files — a rebase/squash candidate). Detection only — no PR is mutated. See #948 / #949 / the #860 post-mortem.
| PR | Title | Triggering metric(s) |
|---|---|---|
| #1819 | chore: sync 4 org-standard workflow stub(s) from petry-projects/.github | open 165h with agent churn (3 cycles, >48h) |
| #1800 | feat: implement issue #1566 — dev-lead reads only the issue title/body — issue comments never reach the prompt, so post-filing steering is silently discarded | open 199h with agent churn (1 cycles, >48h) |
| #1799 | feat: implement issue #1743 — Harness cannot resolve a bot review thread whose correct response is 'no change needed' — false positives block merge permanently | open 199h with agent churn (6 cycles, >48h) |
| #1794 | feat: implement issue #1728 — [Phase 2] Teach the interaction-model section 4 table and validate-interaction-model about a multi-role ingress file | open 199h with agent churn (3 cycles, >48h) |
| #1793 | feat: implement issue #1754 — pr-review counts a human-escalation as a posted review — run reports "1 reviews posted" with nothing on the PR | open 200h with agent churn (2 cycles, >48h) |
| #1770 | feat: implement issue #1766 — [bug] pr-review approves PRs with unresolved threads (violates its own decision gate 4) and double-reviews the same SHA | open 210h with agent churn (4 cycles, >48h) |
Activity