[api-consumption] π GitHub API Consumption Report β 2026-08-07 #53972
Closed
Replies: 1 comment
|
This discussion has been marked as outdated by GitHub API Consumption Report Agent. A newer discussion is available at Discussion #54501. |
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-08-19 Β· Repository: github/gh-aw Β· Run: #32244620148
Today at a Glance (2026-08-07 β most recent available data)
π GitHub API Calls Trend (90 days)
Only one day of run history (2026-08-07, 1,645 calls) fell inside the requested 90-day window, so no multi-day trend line can be drawn yet. This data point is now stored in cache-memory and will anchor the trend as future runs of this report accumulate more days.
π GitHub API Calls by Workflow Trend (30 days)
PR Description Updater (194 calls), PR Sous Chef (182 calls) and Impeccable Skills Reviewer (170 calls) were the top consumers on the only day observed. PR Sous Chef stands out for volume (13 runs) rather than per-run cost, while AI Moderator burned 101 calls in a single run β worth watching as a per-run outlier.
π GitHub REST API Calls Heatmap (90 days)
Since only 2026-08-07 has data, this heatmap shows the hour-of-day distribution for that single day rather than a 90-day weekly pattern. Activity is concentrated in a ~7-hour band (07:00β14:00 UTC), peaking sharply at 13:00 UTC with 533 calls β over 3x the next-busiest hour β with no activity recorded outside that window.
π© Top API Burners (24h)
The top 7 workflows account for 51.9% of all REST API calls, with the remaining 48.1% spread thinly across 49 other workflows β a moderate concentration, not a single dominant consumer. PR Description Updater, PR Sous Chef, and Impeccable Skills Reviewer together make up a third of total consumption.
π GitHub REST API Consumption by Workflow (last 24h)
PR Description Updater, PR Sous Chef, and Impeccable Skills Reviewer lead consumption, but none is close to the 15,000/hr rate limit even concentrated into a single hour (peak hour used 533 calls, ~3.6% of the hourly cap). PR Code Quality Reviewer has the highest average duration (701s) relative to its API footprint (69 calls) β a candidate for reviewing whether its longer runtime is buying proportionate value.
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.
All reactions