[api-consumption] π GitHub API Consumption Report β 2026-04-29 #29218
Closed
Replies: 1 comment
-
|
This discussion has been marked as outdated by GitHub API Consumption Report Agent. A newer discussion is available at Discussion #29758. |
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-29 Β· Repository: github/gh-aw Β· Run: #25139474023
Today at a Glance
π GitHub API Calls Trend (90 days)
This is the first data point in the 90-day tracking history, establishing a baseline of 1,745 core quota API calls on 2026-04-29. Future runs will reveal trend direction and identify peak activity days. The rolling average will become meaningful once 7+ data points are available.
π GitHub API Calls by Workflow Trend (30 days)
With only a single data point available, per-workflow trend analysis will develop over subsequent runs. Today's dominant consumers are Test Quality Sentinel (535 calls, 3 runs) and Smoke CI (435 calls, 3 runs), together accounting for ~56% of all API quota consumed. These workflows are strong candidates to watch for recurring high-consumption patterns.
π GitHub REST API Calls Heatmap (90 days)
The heatmap shows today's top workflows ranked by API consumption. Since this is the initial tracking run, the calendar heatmap will populate as history accumulates. The bar chart fallback clearly shows Test Quality Sentinel and Smoke CI as the highest API consumers, well below the 15k/hr limit.
π© Top API Burners (24h)
Test Quality Sentinel (30.7%) and Smoke CI (24.9%) together dominate 55.6% of today's REST API consumption, reflecting their high-frequency schedule (3 runs each in 24h). The remaining 44% is distributed across 17 other workflows, with Changeset Generator (6.1%) and Smoke Claude (5.4%) as the next-largest consumers. No single workflow presents concentration risk at current volumes.
π GitHub REST API Consumption by Workflow (last 24h)
All 19 distinct workflows remain far below the 15,000/hr hourly limit β the highest single consumer (Test Quality Sentinel) used only 535 calls. The three smoke test failures (Smoke Copilot, Smoke Crush, Smoke Gemini) each consumed 60β66 calls despite not completing successfully, suggesting optimization potential. Changeset Generator's single run at 707s avg and 106 calls may benefit from caching.
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