You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
β οΈWindow note: Today's collection covers a partial ~12h window (2026-06-24T23:22Z β 2026-06-25T11:27Z). The midday segment of 2026-06-24 was lost when the log continuation call timed out; per the collection policy the workflow proceeded with the partial dataset. Day-over-day comparisons below are skewed by this and by inconsistent historical window sizes.
Today at a Glance
Metric
Value
π€ Total Runs
184 (170 β / 14 β)
π― Success Rate
92.4%
π GitHub REST API Calls
87,653 (core quota consumed β reads, writes, and all GitHub API operations; all 184 runs reported core_consumed)
π Safe-Output Writes
unavailable (safe-output counts not present in this collection window)
β± Avg Duration
588s / 9.8m (p95: 1,108s / 18.5m)
π GitHub API Calls Trend (90 days)
Daily core-quota consumption is highly volatile across the 90-day record, ranging from a few hundred calls on quiet days to a one-off spike of ~574k on 2026-06-17. Today's 87,653 over a 12h window is among the higher readings, driven by sustained PR-review activity overnight and into the morning. The 7-day rolling average remains elevated but is heavily influenced by that mid-June outlier rather than a steady upward shift.
π GitHub API Calls by Workflow Trend (30 days)
The PR-quality cluster β Matt Pocock Skills Reviewer, Test Quality Sentinel, PR Code Quality Reviewer, and Design Decision Gate β consistently dominates per-workflow consumption, with Smoke CI and PR Sous Chef close behind. These same workflows reappear at the top nearly every day, confirming that quota usage tracks PR throughput rather than scheduled/daily agents.
π GitHub REST API Calls Heatmap (90 days)
Consumption concentrates on weekdays, mirroring contributor PR activity, with noticeably lighter weekend cells. A small number of cells (the 06-17 spike) stand out as anomalies well above the typical daily band. Most days sit in the low-thousands-to-low-tens-of-thousands range.
The top three workflows account for 43.4% of all core quota consumed in the window, and the top seven PR/CI workflows make up the overwhelming majority. Consumption is concentrated but not dangerously so β no single workflow is anywhere near the 15,000/hr ceiling, with the largest (Matt Pocock Skills Reviewer) averaging ~970 quota/run across 14 runs.
π GitHub REST API Consumption by Workflow (last 24h)
The four PR-review workflows each consumed 12kβ13.6k quota over 13β14 runs, making them the clearest optimisation targets β caching repeated get_file/get_diff reads or narrowing fetched file sets would yield the biggest savings. Averaged over the 12h window total consumption is ~7,300/hr, comfortably under the 15,000/hr limit, so there is no immediate throttling risk.
Top 10 Workflows by REST API Consumption (last 24h)
Workflow
REST API Calls
Runs
Avg Duration
Matt Pocock Skills Reviewer
13,612
14
10.4m
Test Quality Sentinel
12,295
14
8.6m
PR Code Quality Reviewer
12,131
14
11.0m
Design Decision Gate ποΈ
12,006
13
5.7m
Smoke CI
8,403
11
4.5m
PR Description Updater
5,207
5
9.4m
PR Sous Chef
4,982
10
8.6m
Daily Sentrux Report
1,446
1
9.6m
Daily Observability Report for AWF Firewall and MCP Gateway
1,294
1
11.1m
Semantic Function Refactoring
1,291
1
10.6m
Trending Indicators
7-day API trend: β +293.4% vs. previous 7 days (skewed β the prior 7-day window included several low/partial-data days)
30-day API trend: β insufficient consistent data (older entries use mixed window sizes; a clean 30/30 split is not yet available)
GitHub REST API call rate: ~7,300 calls/hr averaged over today's 12h window (hourly limit: 15,000) β ~49% of ceiling, no throttling risk
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
π GitHub API Consumption Report
Report Date: 2026-06-25 Β· Repository: github/gh-aw Β· Run: #28167093357
Today at a Glance
core_consumed)π GitHub API Calls Trend (90 days)
Daily core-quota consumption is highly volatile across the 90-day record, ranging from a few hundred calls on quiet days to a one-off spike of ~574k on 2026-06-17. Today's 87,653 over a 12h window is among the higher readings, driven by sustained PR-review activity overnight and into the morning. The 7-day rolling average remains elevated but is heavily influenced by that mid-June outlier rather than a steady upward shift.
π GitHub API Calls by Workflow Trend (30 days)
The PR-quality cluster β Matt Pocock Skills Reviewer, Test Quality Sentinel, PR Code Quality Reviewer, and Design Decision Gate β consistently dominates per-workflow consumption, with Smoke CI and PR Sous Chef close behind. These same workflows reappear at the top nearly every day, confirming that quota usage tracks PR throughput rather than scheduled/daily agents.
π GitHub REST API Calls Heatmap (90 days)
Consumption concentrates on weekdays, mirroring contributor PR activity, with noticeably lighter weekend cells. A small number of cells (the 06-17 spike) stand out as anomalies well above the typical daily band. Most days sit in the low-thousands-to-low-tens-of-thousands range.
π© Top API Burners (24h)
The top three workflows account for 43.4% of all core quota consumed in the window, and the top seven PR/CI workflows make up the overwhelming majority. Consumption is concentrated but not dangerously so β no single workflow is anywhere near the 15,000/hr ceiling, with the largest (Matt Pocock Skills Reviewer) averaging ~970 quota/run across 14 runs.
π GitHub REST API Consumption by Workflow (last 24h)
The four PR-review workflows each consumed 12kβ13.6k quota over 13β14 runs, making them the clearest optimisation targets β caching repeated
get_file/get_diffreads or narrowing fetched file sets would yield the biggest savings. Averaged over the 12h window total consumption is ~7,300/hr, comfortably under the 15,000/hr limit, so there is no immediate throttling risk.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