[api-consumption] π GitHub API Consumption Report β 2026-07-18 #46418
Closed
Replies: 1 comment
-
|
This discussion has been marked as outdated by GitHub API Consumption Report Agent. A newer discussion is available at Discussion #46594. |
Beta Was this translation helpful? Give feedback.
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-18 Β· Repository: github/gh-aw Β· Run: #29641894872
Today at a Glance
π GitHub API Calls Trend (90 days)
Daily REST API consumption has held a broadly stable band around 70kβ105k/day since early July, with the 7-day rolling average now sitting near 104k. The window is punctuated by three sharp isolated spikes β the largest on 2026-06-17 at ~574k (roughly 5Γ the baseline), plus secondary peaks on Jun 08 (~208k) and Jul 14 (~276k) that each fell back within a day, indicating one-off backfill or bulk-scan bursts rather than a sustained upward shift.
π GitHub API Calls by Workflow Trend (30 days)
Over the last 30 days the heaviest quota consumers are consistently the PR review agents β Impeccable Skills Reviewer, Matt Pocock Skills Reviewer, and PR Code Quality Reviewer β which track together as PR volume ebbs and flows. Smoke CI shows a spikier profile tied to CI activity, while Tidy and PR Sous Chef form a steady mid-tier. No single workflow shows a runaway growth trajectory; the mix is dominated by the same handful of review/quality agents day over day.
π GitHub REST API Calls Heatmap (90 days)
The heatmap shows consumption concentrated on weekdays, consistent with PR- and schedule-driven agents firing against active development. The single darkest cell corresponds to the mid-June spike week; weekend cells are markedly lighter, reflecting reduced PR traffic. No unexpected off-hours or weekend anomalies stand out beyond those known spike days.
π© Top API Burners (24h)
The last 24h of REST API spend is moderately concentrated: the top three workflows (Impeccable Skills Reviewer, Matt Pocock Skills Reviewer, PR Code Quality Reviewer) together account for roughly a third of all core quota consumed, and the top eight cover the large majority. The long tail of smoke tests and daily audits each contributes only a small slice, so optimisation attention is best focused on the review agents at the head of the distribution.
π GitHub REST API Consumption by Workflow (last 24h)
The top REST API consumers are the PR-review family, each in the 9kβ13k range per day across ~10 runs. Even the busiest workflow (Impeccable Skills Reviewer, 13,280 calls) stays well under the 15,000/hour core limit because its usage is spread across many short runs rather than concentrated in one. The clearest optimisation lever is trimming redundant read calls in the reviewer agents β caching PR/file metadata across the review passes would meaningfully cut the top of this chart.
Top 10 Workflows by REST API Consumption (last 24h)
Trending Indicators
π¦ Cache Memory Status
/tmp/gh-aw/cache-memory/trending/api-consumption/history.jsonlAutomatically generated by the api-consumption-report workflow.
Warning
Firewall blocked 1 domain
The following domain was blocked by the firewall during workflow execution:
awmgmcpgSee Network Configuration for more information.
Beta Was this translation helpful? Give feedback.
All reactions