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
β οΈData completeness note: The logs(-1d) collection call hit the 60s bridge deadline. 66 run directories partially downloaded, of which 61 had a parseable run_summary.json. Today's totals are therefore a lower bound for the last 24h (prior days parsed 84β94 runs). Trend figures should be read with this partiality in mind.
Today at a Glance
Metric
Value
π€ Total Runs
61 (55 β / 6 β)
π― Success Rate
90.2%
π GitHub REST API Calls
15,843 (core quota consumed β includes reads, writes, and all GitHub API operations)
π Safe-Output Writes
0 (issues + PRs + comments + discussions created by safe-output tools)
β± Avg Duration
709.5s (p95: 1353.0s)
π GitHub API Calls Trend (90 days)
Over the 90-day window the daily core-quota footprint is dominated by two outlier spikes β ~208k on Jun 8 and a ~573k peak on Jun 16 β against a typical baseline of 20kβ90k calls/day. The 7-day rolling average (orange) has settled back toward ~40k/day heading into July, and today's parsed total of 15,843 sits at the low end of that band, partly a collection-completeness artifact rather than a true drop.
π GitHub API Calls by Workflow Trend (30 days)
The last 30 days are consistently led by the PR-review family β Design Decision Gate, Impeccable / Matt Pocock Skills Reviewers, Test Quality Sentinel, and PR Code Quality Reviewer β which together form the bulk of the stacked area on active weekdays. Smoke CI contributes a steady lower band, while the long tail of daily maintenance workflows barely registers individually. No single workflow shows a runaway upward trajectory.
π GitHub REST API Calls Heatmap (90 days)
Consumption concentrates on weekdays, mirroring PR activity, with weekends noticeably cooler. The hottest cells align with the mid-June spike week. Sparse or missing cells early in the window reflect days before daily tracking stabilised and a couple of partial-collection days (e.g. the very light Jun 30).
PR Sous Chef alone burned 3,916 calls (~25%) of today's parsed quota β the single largest consumer by a wide margin. The next tier (Design Decision Gate, Impeccable Skills Reviewer, Smoke CI, PR Triage Agent) each sit in the 1.3kβ1.6k range. Consumption is moderately concentrated: the top 5 workflows account for roughly two-thirds of the total.
π GitHub REST API Consumption by Workflow (last 24h)
The top consumers are all PR-triggered reviewers plus PR Sous Chef; none came close to the 15,000 calls/hr per-resource ceiling β the largest single-workflow daily total (3.9k across 5 runs) stays comfortably under budget. PR Sous Chef is the clearest optimisation candidate: at ~780 calls/run it may be worth auditing for redundant reads (e.g. repeated collaborator/issue lookups) that could be cached within a run.
Top 10 Workflows by REST API Consumption (last 24h)
Workflow
REST API Calls
Runs
Avg Duration
PR Sous Chef
3,916
5
8m 43s
Design Decision Gate ποΈ
1,630
4
6m 49s
Impeccable Skills Reviewer
1,611
4
10m 30s
Smoke CI
1,567
4
3m 09s
PR Triage Agent
1,303
1
15m 00s
Test Quality Sentinel
928
4
9m 43s
AI Moderator
927
2
18m 07s
Dependabot Burner
903
1
7m 50s
PR Description Updater
789
2
8m 07s
daily-experiment-report
683
1
27m 58s
Trending Indicators
7-day API trend: β +36.3% vs. previous 7 days (inflated by partial-collection days scoring near-zero in the prior window; treat as directional only)
30-day API trend: β (insufficient data) (need 60 daily points for a stable 30-day comparison; 45 collected so far)
GitHub REST API call rate: ~40,266 calls/day over last 7 days (hourly limit: 15,000 per resource)
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-07-03 Β· Repository: github/gh-aw Β· Run: #28657748005
Today at a Glance
π GitHub API Calls Trend (90 days)
Over the 90-day window the daily core-quota footprint is dominated by two outlier spikes β ~208k on Jun 8 and a ~573k peak on Jun 16 β against a typical baseline of 20kβ90k calls/day. The 7-day rolling average (orange) has settled back toward ~40k/day heading into July, and today's parsed total of 15,843 sits at the low end of that band, partly a collection-completeness artifact rather than a true drop.
π GitHub API Calls by Workflow Trend (30 days)
The last 30 days are consistently led by the PR-review family β Design Decision Gate, Impeccable / Matt Pocock Skills Reviewers, Test Quality Sentinel, and PR Code Quality Reviewer β which together form the bulk of the stacked area on active weekdays. Smoke CI contributes a steady lower band, while the long tail of daily maintenance workflows barely registers individually. No single workflow shows a runaway upward trajectory.
π GitHub REST API Calls Heatmap (90 days)
Consumption concentrates on weekdays, mirroring PR activity, with weekends noticeably cooler. The hottest cells align with the mid-June spike week. Sparse or missing cells early in the window reflect days before daily tracking stabilised and a couple of partial-collection days (e.g. the very light Jun 30).
π© Top API Burners (24h)
PR Sous Chef alone burned 3,916 calls (~25%) of today's parsed quota β the single largest consumer by a wide margin. The next tier (Design Decision Gate, Impeccable Skills Reviewer, Smoke CI, PR Triage Agent) each sit in the 1.3kβ1.6k range. Consumption is moderately concentrated: the top 5 workflows account for roughly two-thirds of the total.
π GitHub REST API Consumption by Workflow (last 24h)
The top consumers are all PR-triggered reviewers plus PR Sous Chef; none came close to the 15,000 calls/hr per-resource ceiling β the largest single-workflow daily total (3.9k across 5 runs) stays comfortably under budget. PR Sous Chef is the clearest optimisation candidate: at ~780 calls/run it may be worth auditing for redundant reads (e.g. repeated collaborator/issue lookups) that could be cached within a run.
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.
Warning
Firewall blocked 1 domain
The following domain was blocked by the firewall during workflow execution:
awmgmcpgSee Network Configuration for more information.
Beta Was this translation helpful? Give feedback.
All reactions