[api-consumption] 📊 GitHub API Consumption Report — 2026-06-14 #39215
Closed
Replies: 1 comment
-
|
This discussion has been marked as outdated by GitHub API Consumption Report Agent. A newer discussion is available at Discussion #39373. |
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-06-14 · Repository: github/gh-aw · Run: #27497465056
Today at a Glance
🔗 GitHub API Calls Trend (90 days)
Total REST API consumption is trending up over the last week (7-day rolling average climbing from ~40k toward ~70k), driven by a sharp spike to 207,880 calls on 2026-06-09 — the single busiest day on record. Outside that peak the series is volatile, alternating between ~15k and ~80k days. The final point (2026-06-14) sits low only because it captures a partial, in-progress day.
🔗 GitHub API Calls by Workflow Trend (30 days)
A small set of write-heavy workflows dominates quota consumption day to day, with Smoke CI, PR Sous Chef, and the design/review gate workflows recurring as top burners. Most workflows stay well below 1k calls per run; the spikes track CI-heavy and PR-automation days rather than any single runaway workflow.
🔗 GitHub REST API Calls Heatmap (90 days)
Consumption concentrates on weekdays, with the heaviest cells landing mid-to-late in the working week — consistent with development and PR activity driving most API traffic. Weekend cells are consistently lighter. The standout hot cell corresponds to the 2026-06-09 spike, which reads as an anomaly against the surrounding weeks rather than a sustained shift.
🍩 Top API Burners (24h)
Consumption in the last 24h is highly concentrated: PR Sous Chef (43%) and AI Moderator (24%) together account for two-thirds of all REST API calls, with Contribution Check and the AIC Usage Audit adding another 20%. This concentration means optimisation effort on just the top two workflows would move the overall number the most.
🔗 GitHub REST API Consumption by Workflow (last 24h)
PR Sous Chef (3,190 calls over 10 runs) and AI Moderator (1,746 over 5 runs) are the clear top consumers, but both remain far below the 15,000-calls/hour core limit — no workflow is anywhere near the ceiling in this window. PR Sous Chef's ~319 calls/run is the most attractive optimisation target if per-run API chatter is worth trimming.
Top 10 Workflows by REST API Consumption (last 24h)
Trending Indicators
Failed (4):
All four failures consumed negligible API quota (≤6 calls each), so the failures are not API-driven. In-progress (2): Daily Documentation Updater, GitHub API Consumption Report Agent (this run).
📦 Cache Memory Status
/tmp/gh-aw/cache-memory/trending/api-consumption/history.jsonl-90drequest timed out after the most recent 84 runs / ~12h; existing history already covers the full tracking window back to 2026-05-18, so today's entry was upserted incrementally)Automatically generated by the api-consumption-report workflow.
Beta Was this translation helpful? Give feedback.
All reactions