[api-consumption] 📊 GitHub API Consumption Report — 2026-07-31 #49325
Closed
Replies: 1 comment
|
This discussion has been marked as outdated by GitHub API Consumption Report Agent. A newer discussion is available at Discussion #49569. |
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-31 · Repository: github/gh-aw · Run: #30627363449
Today at a Glance
safe_items_countrecorded in today'srun_summary.jsonfiles — see cache status note below)🔗 GitHub API Calls Trend (90 days)
Total REST API consumption has climbed steadily over the tracked window, with today's 96,770 calls sitting well above the 7-day average — consistent with the +13.8% 7-day trend below. The 30-day trend (+47.5%) shows the steepest growth phase occurred in the back half of the window as more agentic workflows came online.
🔗 GitHub API Calls by Workflow Trend (30 days)
Review-and-quality workflows (Test Quality Sentinel, PR Code Quality Reviewer, Design Decision Gate, Matt Pocock Skills Reviewer) dominate sustained API consumption over the last 30 days, each running many times per day against active PRs. Their combined share suggests PR-triggered review workflows are the primary driver of quota growth, rather than any single scheduled job.
🔗 GitHub REST API Calls Heatmap (90 days)
Weekday activity is noticeably heavier than weekends, tracking normal PR/commit cadence. Recent weeks show darker cells overall compared to the start of the tracked window, reflecting the steady upward trend rather than isolated spike days.
🍩 Top API Burners (24h)
The top 10 workflows account for the large majority of today's 96,770 calls, led by Test Quality Sentinel (~10%) and Design Decision Gate (~9%). No single workflow dominates outright, but the concentration in PR-review-triggered workflows means a burst of PR activity could push quota usage up quickly.
🔗 GitHub REST API Consumption by Workflow (last 24h)
Test Quality Sentinel (9,745 calls across 12 runs) and Design Decision Gate (8,698 across 9 runs) are today's top consumers, both well under the 15k/hr hourly limit individually. Since these workflows fire on PR events rather than a fixed schedule, coordinating review-workflow triggers (e.g. batching or debouncing) could reduce redundant API calls during periods of high PR churn.
Top 10 Workflows by REST API Consumption (last 24h)
Trending Indicators
📦 Cache Memory Status
/tmp/gh-aw/cache-memory/trending/api-consumption/history.jsonlNote: the
logsMCP tool call forstart_date=-1dprinted aGH_TOKEN not set, using GITHUB_TOKEN for gh CLIerror after ~300s, but the run-log directories for 2026-07-30/2026-07-31 (523 directories, 191 withaw_info.json) were already present on disk and were used as the authoritative dataset for this report, per the "treat directories already on disk as authoritative" guidance. No continuation paging was needed since a single window call covered both days. Thegithub_safe_output_callsmetric is 0 today and yesterday becauserun.safe_items_countis absent from therun_summary.jsonfiles in this dataset — this looks like an upstream schema/data-population gap in the safe-outputs pipeline, not a real drop to zero writes, and is worth a follow-up look if the value stays at 0 in future runs.Automatically generated by the api-consumption-report workflow.
All reactions