[api-consumption] 📊 GitHub API Consumption Report — 2026-05-30 #35907
Closed
Replies: 1 comment
-
|
This discussion has been marked as outdated by GitHub API Consumption Report Agent. A newer discussion is available at Discussion #36106. |
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-05-30 · Repository: github/gh-aw · Run: #26682250918
Today at a Glance
Today's REST API footprint (17,750 core-quota calls across 63 runs) is the lowest in the tracked window, continuing a steady decline from the 2026-05-27 peak of ~118K. Success rate held at a healthy 88.9% (7 failures), and safe-output writes ticked up to 79 — the highest in the window.
🔗 GitHub API Calls Trend (90 days)
Daily REST API consumption peaked sharply at 118K on 2026-05-27 and has fallen every day since, down to 17,750 today. The 7-day rolling average (orange) is now trending downward, indicating the late-May spike was a transient burst rather than a sustained shift. The tracked window currently spans 12 days (since 2026-05-18); the curve will extend toward a true 90-day view as history accrues.
🔗 GitHub API Calls by Workflow Trend (30 days)
The smoke-test family (Smoke Copilot / Claude / Gemini / Pi / Antigravity / CI) and PR Sous Chef are the most consistent day-over-day consumers of REST API quota. No single workflow exhibits runaway growth; per-workflow daily consumption stays clustered well below the total-calls average line, so the aggregate trend is driven by run volume rather than any one heavy workflow.
🔗 GitHub REST API Calls Heatmap (90 days)
Only 12 days of history are available so far (< 14 points), so this panel renders the fallback view: today's top workflows by REST API consumption. Once ≥ 14 daily data points accumulate, this will switch to a calendar-style 90-day heatmap revealing weekday/weekend patterns and busiest days.
🍩 Top API Burners (24h)
API consumption today is evenly distributed — the top burners (Smoke Copilot, PR Sous Chef, Smoke Claude/Gemini/Antigravity, Changeset Generator, Agent Container Smoke Test, Smoke Pi) each account for roughly 6–7% of the daily total. There is no concentration risk: no workflow dominates the quota, and the long tail of dozens of low-consumption workflows makes up the remainder.
🔗 GitHub REST API Consumption by Workflow (last 24h)
The heaviest consumer, Smoke Copilot (1,224 calls), sits at barely 8% of the 15,000/hr core limit — every workflow is comfortably within budget. The smoke-test suite collectively consumes the most quota but does so across short, independent runs, so there is no immediate optimisation pressure. PR Sous Chef is notable for spreading 1,154 calls across 6 runs (~192/run).
Top 10 Workflows by REST API Consumption (last 24h)
Trending Indicators
📦 Cache Memory Status
/tmp/gh-aw/cache-memory/trending/api-consumption/history.jsonl-90d; the logs fetch timed out after returning only today's runs, so today was appended incrementally — older days were not retrievable within the fetch window)Automatically generated by the api-consumption-report workflow.
Beta Was this translation helpful? Give feedback.
All reactions