You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This week, github/gh-aw saw 1,327 issues created in the last 7 days. The burst was overwhelmingly automation-driven: 1,303 were opened by github-actions[bot], leaving 193 open and 1,134 closed. Most of the volume came from repetitive workflow and triage tasks rather than individual feature work.
Key metrics
Total opened: 1,327
Open now: 193
Closed this week: 1,134
Top authors: github-actions[bot] (1,303), dsyme (11), davidslater (5), lpcox (4)
Common prefixes: [aw] (503), [WIP] (218), [deep-report] (106), [squad:plan] (47)
📈 Issue Activity Trends
Weekly Activity Patterns
The backlog grew quickly in the first half of the window and then flattened as the automation stack closed out a large share of the generated work. The pattern suggests high-volume issue churn from routine checks rather than a sustained increase in product-level work.
Resolution Time Analysis
Resolution times stayed relatively consistent across the week, with average close times clustering in a manageable range. The main signal is not a slowdown in closure but the high rate of bot-generated issue creation overwhelming the backlog.
Patterns and trends
Routine automation dominated the week: daily workflow failures, test parallelizer failures, and missing-tool reports were the most common issue themes.
The repo also saw project-planning and audit-style issues, especially around Morrow Mosaic planning and deep-report investigations.
The human-authored set was small and concentrated in repo quality, workflow, and engineering follow-up work.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Overview
This week, github/gh-aw saw 1,327 issues created in the last 7 days. The burst was overwhelmingly automation-driven: 1,303 were opened by github-actions[bot], leaving 193 open and 1,134 closed. Most of the volume came from repetitive workflow and triage tasks rather than individual feature work.
Key metrics
📈 Issue Activity Trends
Weekly Activity Patterns
The backlog grew quickly in the first half of the window and then flattened as the automation stack closed out a large share of the generated work. The pattern suggests high-volume issue churn from routine checks rather than a sustained increase in product-level work.
Resolution Time Analysis
Resolution times stayed relatively consistent across the week, with average close times clustering in a manageable range. The main signal is not a slowdown in closure but the high rate of bot-generated issue creation overwhelming the backlog.
Patterns and trends
Representative issues
Representative issue inventory
@github-actions[bot]@github-actions[bot]@github-actions[bot]@github-actions[bot]@github-actions[bot]@github-actions[bot]@github-actions[bot]@github-actions[bot]@github-actions[bot]Recommendations
Warning
Firewall blocked 1 domain
The following domain was blocked by the firewall during workflow execution:
ab.chatgpt.comTo allow these domains, add them to the
network.allowedlist in your workflow frontmatter:See Network Configuration for more information.
All reactions