[api-consumption] 📊 GitHub API Consumption Report — 2026-04-28 #29006
Closed
Replies: 2 comments 1 reply
-
|
/q fix caching. This should have more data available. |
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 #29218. |
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-28 · Repository: github/gh-aw · Run: #25083284908
Today at a Glance
🔗 GitHub API Calls Trend (90 days)
This is the first data point in the tracking history — baseline established at 17,456 REST API calls. With only one day of data, trend direction cannot yet be determined. Future reports will reveal whether this is a typical day or an outlier.
🔗 GitHub API Calls by Workflow Trend (30 days)
Insufficient history for a multi-day workflow trend (first run). The Agentic Workflow Audit Agent and Copilot CLI Deep Research Agent are the two highest single-run consumers today at 3,498 and 2,384 calls respectively. As history accumulates, this chart will show which workflows consistently dominate API consumption.
🔗 GitHub REST API Calls Heatmap (90 days)
First data point — no weekly patterns observable yet. Today's total of 17,456 calls provides the baseline. The fallback bar chart shows today's per-workflow breakdown, which will transition to a full calendar heatmap once 14+ days of history are available.
🍩 Top API Burners (24h)
The Agentic Workflow Audit Agent alone accounts for 20% of today's REST API consumption (3,498 of 17,456 calls). The top 4 workflows — Audit Agent, Copilot Deep Research, Test Quality Sentinel, and Contribution Check — collectively consume 57% of total calls, indicating moderate concentration risk. Monitoring these workflows for optimisation opportunities would yield the greatest quota savings.
🔗 GitHub REST API Consumption by Workflow (last 24h)
No individual workflow exceeds the 15k/hr limit. The total across all 45 runs was 17,456 — spread over 24 hours — well within safe bounds. The Agentic Workflow Audit Agent (3,498 calls, ~1,646s avg) and Copilot CLI Deep Research Agent (2,384 calls, ~765s avg) are the top targets for API call optimisation if quota headroom becomes a concern.
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