[api-consumption] 📊 GitHub API Consumption Report — 2026-04-24 #28370
Closed
Replies: 2 comments 1 reply
-
|
/q fix the prompt to ensure that caching and round robin works. Validate that a cache is created in previous runs. |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
🔧 Pay attention, 007! Q is preparing your gadgets for this discussion comment... |
Beta Was this translation helpful? Give feedback.
-
|
This discussion has been marked as outdated by GitHub API Consumption Report Agent. A newer discussion is available at Discussion #28523. |
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-04-24 · Repository: github/gh-aw · Run: §24916593308
Today at a Glance
🔗 GitHub API Calls Trend (90 days)
This is the first day of tracking, establishing a baseline of 9,979 core quota calls. No prior data exists for trend comparison. As daily runs accumulate, the rolling 7-day average overlay will reveal consumption patterns. Today's total remains comfortably below the 15,000/hr GitHub REST API rate limit.
🔗 GitHub API Calls by Workflow Trend (30 days)
With only one day of history, per-workflow trends are not yet visible. Test Quality Sentinel and Design Decision Gate are the clear leaders today at 2,470 and 1,880 core calls respectively — together consuming 44% of the day's total. Workflow trend lines will populate as tracking continues across subsequent runs.
🔗 GitHub REST API Calls Heatmap (90 days)
As this is the first collection day, the chart displays today's top workflows as a bar chart (calendar heatmap requires ≥14 days of data). Activity is driven primarily by scheduled nightly workflows and event-triggered CI runs. The calendar heatmap will activate once sufficient history is collected, revealing weekly and monthly patterns in REST API consumption.
🍩 Top API Burners (24h)
Test Quality Sentinel (24.8%) and Design Decision Gate (18.8%) dominate the 24-hour API footprint, together accounting for 43.6% of all core quota consumed. The top 3 workflows (including Smoke CI at 15.6%) collectively consume nearly 60% of today's total — indicating a high concentration of API load in event-driven quality-gate workflows that run on every PR/push.
🔗 GitHub REST API Consumption by Workflow (last 24h)
The highest single-workflow consumer is Test Quality Sentinel at 2,470 calls across 4 runs — well below the 15k/hr limit. The Release workflow stands out for the longest single-run duration (30.2m), suggesting it performs extensive repository queries during a release cycle. Smoke test workflows (Claude, Codex, Copilot, OpenCode) each consume modest API budgets (< 200 calls) but collectively add up across frequent runs.
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.
Beta Was this translation helpful? Give feedback.
All reactions