Repository navigation
[deep-report] Add repeat-offender detection to the automated [aw] workflow-failure issue filer #48672
Closed as not planned
Description
Activity
- added a parent issue
on Jul 28, 2026 🍪 Issue Monster selected this for Copilot
I have identified this issue as a good candidate for automated resolution and requested assignment to the Copilot coding agent.
If assignment succeeds, the Copilot coding agent will analyze the issue and create a pull request with the fix.
Om nom nom! 🍪
🍪 Om nom nom by Issue Monster · gpt54 · 2.45 AIC · ⌖ 5.64 AIC · ⊞ 7K · ◷
- linked a pull request that will close this issueConsolidate repeat workflow-failure issues by reusing/reopening recent threads #48701
on Jul 28, 2026 This issue was automatically closed because it expired on 2026-07-30T15:41:43.027Z.
Closed by Workflow
Description
Across this week's data, the same workflow failing repeatedly gets a brand-new siloed
[aw] <workflow> failed/produced no safe outputsissue every time instead of being linked/consolidated: Matt Pocock Skills Reviewer (9+ issues since 07-25), Design Decision Gate (3+ issues), and Daily Container Image Security Scan (4 issues: #47939, #48152, #48311, #48549) all show this pattern. This mirrors the same anti-pattern DeepReport's own prior run (#47811) had to manually clean up for goroutine/timeout fixes.Expected Impact
When the automated failure detector is about to file an issue for a workflow that already has an open failure issue from the last N days, it should comment/re-open the existing issue instead of creating a new one. This directly reduces backlog noise and makes chronic failures visible as a single trend line instead of N disconnected data points.
Suggested Agent
New Agent (or extend the existing
[aw]failure-detection automation).Estimated Effort
Medium (1-4 hours)
Data Source
DeepReport Intelligence Briefing analysis, 2026-07-28. Cross-referenced patterns: Matt Pocock Skills Reviewer, Design Decision Gate, Daily Container Image Security Scan issue histories.