Organization Health Report - 2026-09-14 (scope-limited) #60797
Closed
Replies: 1 comment
|
This discussion was automatically closed because it expired on 2026-09-15T08:50:46.551Z.
|
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.
🏥 Organization Health Report — 2026-09-14
Within the accessible scope, this run analyzed 171 issues and 123 PRs. Volume is dominated by
gh-awandgh-aw-mcpg, both high-churn automation/agentic-workflow repos with frequent bot-driven issue/PR creation (failure reports, dependabot updates, agent-run bookkeeping).📊 Volume Metrics
Overall Status (accessible repos)
🏆 Top Active Repositories (accessible scope)
gh-awandgh-aw-mcpgaccount for the vast majority of activity — expected, as these are the primary agentic-workflow development/testing repos with continuous automated issue/PR generation from CI smoke tests and dependabot.Top Active Authors
Note:
github-actions[bot],Copilot, anddependabot[bot]dominate — reflecting heavy automation (CI failure reports, agent-created PRs, dependency bumps) rather than human contributor volume.🔥 High-Activity Unresolved Items
Hot Issues (Need Attention)
Hot PRs (Need Review)
💡 Commentary and Recommendations
gh-aw/gh-aw-mcpgCI/agent-run bookkeeping. To produce a real org-wide report, this workflow needs broader read access (e.g. a token/policy update allowingsearch/issuesandrepos/*/issuesacross all publicgithuborg repos).gh-aw/gh-aw-mcpg(117 and 40 issues respectively in the observed window) suggests frequent CI/smoke-test failures are being auto-filed. Maintainers should review whether failure-report issues are being triaged/closed promptly, since 0% of open issues currently carry assignees.Full Data and Methodology
Data Collection
githuborg repos discovered viagh search repos --owner githubMethodology
gh search repos --owner github --sort updated --limit 100gh api search/issueswithorg:github is:issue|pr is:open|closedqueriesrepos/{owner}/{repo}/issues) returned empty for most of the ~75 repos outside the accessible allowlist, confirming a firewall/policy restriction rather than a data-availability issueAll reactions