[Issue Arborist] Issue Arborist Run Summary #2152
Closed
Replies: 1 comment
|
This discussion has been marked as outdated by Issue Arborist. A newer discussion is available at Discussion #2159. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
🌳 Issue Arborist Report
Issues analyzed: 67
Parent issues created
None this run — no orphan cluster of 5+ unparented issues was found; all qualifying clusters already had an existing parent issue that simply hadn't linked its listed children yet.
Links created
Note: #1428 and #1321 both legitimately reference #1103/#381/#471 — the umbrella issues describe overlapping scopes (safe-output tool correctness vs. MCPG+safe-output tooling), so both links were kept as each parent's own body explicitly calls them out.
30 links created this run, reaching the per-run cap.
Suggested (not linked — for maintainer review)
Observations
[Parent]umbrella issues; most just needed their previously-listed related issues formally linked as GitHub sub-issues, which this run did.[Parent]issues underrepresent recent activity — [Parent] Track and resolve recurring agentic workflow execution failures (non-rate-limit) #1549 in particular can absorb more recent[aw]failure issues than were linked here due to the cap.All reactions