[api-consumption] 📊 GitHub API Consumption Report — 2026-06-12 #38829
Closed
Replies: 1 comment
-
|
This discussion has been marked as outdated by GitHub API Consumption Report Agent. A newer discussion is available at Discussion #39067. |
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-12 · Repository: github/gh-aw · Run: #27413958124
Today at a Glance
🔗 GitHub API Calls Trend (90 days)
Daily REST API consumption climbed steadily through late May into early June, with a pronounced spike on 2026-06-09 (~207.9k calls) — the single busiest day in the tracked window. The 7-day rolling average sits well above the 30-day baseline, confirming an upward trajectory; the apparent dip at the right edge is the partial-day artifact for today and should not be read as a real decline.
🔗 GitHub API Calls by Workflow Trend (30 days)
Consumption is spread across a long tail of workflows, but a handful of recurring CI and PR-automation jobs (e.g. Smoke CI, PR Description Updater) dominate the stacked totals on most days. The "Other" band remains substantial, indicating that no single workflow monopolises the quota — broad, distributed usage rather than one runaway consumer.
🔗 GitHub REST API Calls Heatmap (90 days)
The heatmap shows consumption concentrated on weekdays, with the heaviest cells mid-week, tapering off over weekends. The standout hot cell aligns with the 2026-06-09 spike. No unexpected weekend bursts appear, consistent with development-driven, business-hours activity.
🍩 Top API Burners (24h)
In the last 24h, Smoke CI and PR Description Updater together account for roughly two-thirds of all REST API quota consumed, making them the clear concentration points. The remaining workflows each contribute a modest single-digit-percent share, so optimisation effort is best focused on those top two consumers.
🔗 GitHub REST API Consumption by Workflow (last 24h)
The top consumers — Smoke CI (2,643) and PR Description Updater (2,497) — sit far below the 15,000/hr core limit, so there is no immediate throttling risk. Smoke CI's cost is amortised across 3 runs; PR Description Updater spends ~1.25k per run, the highest per-run footprint and the best candidate for caching or request-batching.
Top 10 Workflows by REST API Consumption (last 24h)
Trending Indicators
📦 Cache Memory Status
/tmp/gh-aw/cache-memory/trending/api-consumption/history.jsonlstart_date=-90d; the logs download timed out after 120s, so only the most recent runs — all dated 2026-06-12 — were retrieved. The existing 24-day history was preserved and today's entry appended.)Automatically generated by the api-consumption-report workflow.
Beta Was this translation helpful? Give feedback.
All reactions