[api-consumption] π GitHub API Consumption Report β 2026-07-20 #46808
Closed
Replies: 2 comments
-
|
Smoke test comment
|
Beta Was this translation helpful? Give feedback.
0 replies
-
|
This discussion has been marked as outdated by GitHub API Consumption Report Agent. A newer discussion is available at Discussion #47065. |
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-07-20 Β· Repository: github/gh-aw Β· Run: #29739077610
Today at a Glance
π GitHub API Calls Trend (90 days)
Daily REST consumption has settled into a stable 75kβ105k band over the past week, with today at 85,565 calls β essentially flat versus yesterday's 87,642. The only major outlier remains 2026-07-15 (275,797 calls), flagged as a >2Ο anomaly, which continues to inflate short-window averages. Outside that spike, the trend is steady with no sign of runaway growth.
π GitHub API Calls by Workflow Trend (30 days)
The PR-triggered review family β Matt Pocock Skills Reviewer, Impeccable Skills Reviewer, PR Code Quality Reviewer, and Design Decision Gate β consistently leads consumption, each tracking closely with PR volume day to day. Tidy and PR Description Updater show spikier, lower-frequency footprints tied to burst activity rather than steady load.
π GitHub REST API Calls Heatmap (90 days)
Consumption concentrates on weekdays, mirroring PR and CI activity, with visibly lighter weekend cells. The mid-July week stands out with the darkest cell driven by the 07-15 spike, while surrounding weeks stay in the moderate range β no persistent hot streak beyond that single day.
π© Top API Burners (24h)
The top three burners β the two Skills Reviewers and Design Decision Gate β each consume roughly 10k calls and together account for about 36% of the day's total. The top eight workflows dominate the pie, so consumption is moderately concentrated but not dangerously reliant on any single workflow.
π GitHub REST API Consumption by Workflow (last 24h)
No workflow comes close to the 15,000/hr limit β the heaviest (Matt Pocock Skills Reviewer) tops out near 10.5k spread across 11 runs, so per-run consumption is well within bounds. PR Description Updater stands out for efficiency risk: 8,122 calls over only 4 runs (~2k/run), making it the highest per-run consumer and a good candidate for caching or narrowing its GitHub queries.
Top 10 Workflows by REST API Consumption (last 24h)
Trending Indicators
π¦ Cache Memory Status
/tmp/gh-aw/cache-memory/trending/api-consumption/history.jsonllogsMCP call reported an HTTP timeout, but 140 run directories were successfully written to disk before the transport error and were used as the authoritative dataset (per the collection guidance). No continuation paging was performed.run_summary.jsonβgithub_rate_limit_usage.core_consumed; safe-output writes from each run'ssummary.jsonβsafe_outputs.total_items.Automatically 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