[api-consumption] π GitHub API Consumption Report β 2026-07-21 #47065
Closed
Replies: 1 comment
|
This discussion has been marked as outdated by GitHub API Consumption Report Agent. A newer discussion is available at Discussion #47283. |
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-07-21 Β· Repository: github/gh-aw Β· Run: #29825753050
Today at a Glance
π GitHub API Calls Trend (90 days)
Daily REST API consumption remains volatile but the 7-day rolling average has climbed steadily since early July, now sitting near 118k/day. The standout remains the 574k spike on Jun 17 β roughly 6Γ a normal day β with secondary bursts on Jul 04 (183k) and the 276k peak on Jul 14. Today's 90,320 calls land just below the rolling average, a calmer day after that mid-July surge.
π GitHub API Calls by Workflow Trend (30 days)
The PR-review family β Design Decision Gate, the two Skills Reviewers, PR Code Quality Reviewer, and Test Quality Sentinel β consistently tops the by-workflow ranking day after day, tracking PR activity. Tidy shows spikier behaviour: low most days, then occasional large single-run bursts (11k today across just 9 runs). No new workflow has broken into the top tier over the last 30 days.
π GitHub REST API Calls Heatmap (90 days)
Consumption concentrates on weekdays, mirroring PR and development activity, with weekends noticeably cooler. The single darkest cell corresponds to the mid-June 574k anomaly, which dominates the color scale and makes routine daily variation appear muted by comparison. The most recent two weeks show a consistent warm weekday band, in line with the rising rolling average.
π© Top API Burners (24h)
The top 7 named workflows account for ~81% of today's 90,320 calls, with a long tail ("Other" = 19%) spread across ~78 low-volume workflows. No single workflow dominates β the leader, Design Decision Gate at 14%, is closely trailed by Tidy, Test Quality Sentinel, and both Skills Reviewers (11β12% each). Concentration risk is moderate: the PR-review cluster collectively drives the majority of quota.
π GitHub REST API Consumption by Workflow (last 24h)
The five PR-review workflows plus Tidy each consume ~9kβ13k calls/day. No single run approached the 15,000/hr limit on its own (heaviest single run: Test Quality Sentinel at 653). However, the shared hourly quota dipped as low as 267 remaining during a busy window β evidence that concentrated bursts of many small runs (PR Triage, Sub-Issue Closer, Issue Monster firing together) can crowd the per-hour ceiling. Optimisation opportunity: stagger or debounce the PR-review cluster so multiple reviewers don't fan out on the same PR event simultaneously.
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.
All reactions