[api-consumption] 📊 GitHub API Consumption Report — 2026-08-15 #52879
Closed
Replies: 1 comment
|
This discussion has been marked as outdated by GitHub API Consumption Report Agent. A newer discussion is available at Discussion #53354. |
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-15 · Repository: github/gh-aw · Run: #31880421320
Today at a Glance
🔗 GitHub API Calls Trend (90 days)
Only 5 days of trending history exist so far (2026-08-11 through 2026-08-15), so this chart shows the full available window rather than a true 90-day trend. Calls swung from a low of ~71K (Aug 12) to a high of ~206K (Aug 15, today) — today is the highest single day recorded, driven largely by heavier PR-review workflow activity. No sustained multi-week trend can be established yet; that will become meaningful as more daily snapshots accumulate.
🔗 GitHub API Calls by Workflow Trend (30 days)
Across the 5 days of data available, PR Sous Chef consistently ranks among the top consumers and spiked sharply today (~30.5K calls, more than double its prior daily levels). Impeccable Skills Reviewer, Matt Pocock Skills Reviewer, Design Decision Gate, and PR Code Quality Reviewer cluster tightly together most days (10–20K range), suggesting these review-style workflows have similar, predictable per-run costs.
🔗 GitHub REST API Calls Heatmap (90 days)
With fewer than 14 days of history, the calendar heatmap fell back to a bar chart of today's top workflows by REST API consumption. PR Sous Chef (30,543) and PR Description Updater (25,116) are the clear standouts — together they account for roughly 27% of all API calls in the last 24 hours, well ahead of the rest of the pack which cluster in the 6K–10.5K range.
🍩 Top API Burners (24h)
PR Sous Chef (14.8%) and PR Description Updater (12.2%) together consume 27% of today's total REST API quota from just 2 workflows out of dozens active. The "other" bucket (37.2%, 76,812 calls) is spread across many lower-volume workflows, so concentration risk is moderate — the top 2 dominate, but no single workflow exceeds 15%.
🔗 GitHub REST API Consumption by Workflow (last 24h)
PR Sous Chef (30,543 calls across 34 runs, ~898/run) is the top consumer, followed by PR Description Updater (25,116 across just 9 runs, ~2,791/run — the highest per-run cost among top workflows). All workflows remain comfortably under the 15,000/hour rate limit reference line even at their 24h totals; per-run PR Description Updater cost is worth watching if its run frequency increases.
Top 10 Workflows by REST API Consumption (last 24h)
Trending Indicators
📦 Cache Memory Status
/tmp/gh-aw/cache-memory/trending/api-consumption/history.jsonlrun_summary.json). This repository has very high daily run volume, so a full 90-day backfill was not achievable within the continuation-call budget. The trending charts above rely on the smaller cache-memory history (5 days) built up across daily runs of this workflow rather than a single full backfill.Automatically generated by the api-consumption-report workflow.
All reactions