[api-consumption] π GitHub API Consumption Report β 2026-07-24 #47776
Closed
Replies: 1 comment
|
This discussion has been marked as outdated by GitHub API Consumption Report Agent. A newer discussion is available at Discussion #47983. |
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.
π GitHub API Consumption Report
Report Date: 2026-07-24 Β· Repository: github/gh-aw Β· Run: #30089058566
Today at a Glance
π GitHub API Calls Trend (90 days)
Total REST API consumption is trending up sharply over 30 days (β +46%) while holding roughly flat week-over-week (β +4.5%). Today's 169.8K is the highest reading since early July and well above the ~107K/day 7-day average, though still far below the 574K spike on 2026-06-17. The pattern is spiky rather than steadily rising β a handful of heavy days dominate.
π GitHub API Calls by Workflow Trend (30 days)
The heaviest consumers are consistently the PR review-oriented workflows β PR Code Quality Reviewer, Test Quality Sentinel, and the two Skills Reviewers β which together drive most day-to-day variance. Daily totals track the number of open PRs being reviewed, so quota tends to rise with PR activity rather than with any single runaway workflow.
π GitHub REST API Calls Heatmap (90 days)
Consumption is concentrated on weekdays, with weekends noticeably lighter β consistent with PR-driven review traffic. The mid-June week stands out as the single hottest cell, matching the 574K spike, while the most recent two weeks show a broad, sustained warm band across working days.
π© Top API Burners (24h)
The top consumer, PR Code Quality Reviewer (15.2K, ~9%), leads a fairly distributed field β no single workflow dominates, and the top ~7 review/PR workflows each hold a similar single-digit-percent share. Concentration risk is low; the long tail of smoke tests and daily agents collectively forms the
otherslice.π GitHub REST API Consumption by Workflow (last 24h)
PR Code Quality Reviewer (15,240) nominally edges past the 15K/hr reference line, but that total is spread across 12 runs over 24h (~1,270/run), so no individual run approaches the hourly ceiling. Four workflows exceed 10K/day; the clearest optimisation lever is trimming per-review GitHub reads in the PR review workflows (caching PR file lists / diffs) since they collectively account for the bulk of quota.
Top 10 Workflows by REST API Consumption (last 24h)
Trending Indicators
π¦ Cache Memory Status
/tmp/gh-aw/cache-memory/trending/api-consumption/history.jsonlπ Safe-Output Writes by Type (24h, top)
add_comment 118 Β· create_issue 113 Β· update_pull_request 55 Β· create_pull_request_review_comment 52 Β· submit_pull_request_review 44 Β· create_discussion 33 Β· add_labels 26 Β· create_pull_request 14 Β· resolve_pull_request_review_thread 9 Β· assign_to_agent 8 β 509 total items actuated
Automatically generated by the api-consumption-report workflow.
All reactions