[api-consumption] 📊 GitHub API Consumption Report — 2026-06-03

[github-actions[bot]]

📊 GitHub API Consumption Report

Report Date: 2026-06-03 · Repository: github/gh-aw · Run: #26884195726

---

Today at a Glance

Metric	Value
🤖 Total Runs	157 (140 ✅ / 16 ❌)
🎯 Success Rate	89.2%
🔗 GitHub REST API Calls	84,224 (core quota consumed — includes reads, writes, and all GitHub API operations)
📝 Safe-Output Writes	150 (issues + PRs + comments + discussions created by safe-output tools)
⏱ Avg Duration	465.4s (p95: 959.4s)

---

🔗 GitHub API Calls Trend (90 days)

Today's 84,224 REST API calls mark a sharp rebound from the 16-day low of 17,043 on Jun 2, driven by a heavy PR-triggered workload (157 runs vs. 54 the day before). Even so, daily volume stays well under the May 27 peak of 118,077, and the 7-day rolling average continues to drift downward (−35.4% vs. the prior week). Consumption remains bursty rather than steadily rising, tracking PR activity rather than scheduled jobs.

---

🔗 GitHub API Calls by Workflow Trend (30 days)

The top consumers are consistently the PR-gated workflows — Smoke CI, PR Code Quality Reviewer, Design Decision Gate, and PR Description Updater — which spike on busy PR days and fall near zero on quiet ones. Scheduled/daily workflows contribute a comparatively flat, low baseline. The emerging pattern is clear: API quota is dominated by per-PR fan-out, so consumption scales with contributor activity, not with the size of the scheduled fleet.

---

🔗 GitHub REST API Calls Heatmap (90 days)

The heaviest cells cluster in the second half of May (ISO weeks 21–22), peaking on Tuesday May 27. The current week (W23) shows renewed mid-week intensity on today's Wednesday cell. Weekends remain consistently lighter, reflecting reduced PR throughput outside working days — no unexplained off-hours anomalies are present.

---

🍩 Top API Burners (24h)

Smoke CI alone accounts for ~17.9% of today's REST API calls, and the top three workflows (Smoke CI, PR Code Quality Reviewer, Design Decision Gate) together make up ~37.7%. The remaining ~62% is spread across a long tail of 79 other workflows, so concentration is moderate — no single workflow is a runaway, but the PR-review cluster is worth watching as PR volume grows.

---

🔗 GitHub REST API Consumption by Workflow (last 24h)

Smoke CI tops the list at 15,040 calls across 20 runs (~752/run), followed by PR Code Quality Reviewer (8,866) and Design Decision Gate (7,881). No workflow approached the 15,000/hour core limit at run granularity — the 15,040 figure is a full-day total spread across many runs. The clearest optimisation target is Smoke CI's 20 daily runs: conditional or debounced triggering on PR events could meaningfully trim quota without reducing coverage.

---

Top 10 Workflows by REST API Consumption (last 24h)

Workflow	REST API Calls	Runs	Avg Duration
Smoke CI	15,040	20	179.2s
PR Code Quality Reviewer	8,866	10	478.0s
Design Decision Gate 🏗️	7,881	10	292.3s
PR Description Updater	6,585	7	298.1s
Matt Pocock Skills Reviewer	3,875	10	442.2s
AI Moderator	3,379	2	920.5s
Test Quality Sentinel	3,261	10	378.0s
Daily A/B Testing Advisor	2,620	1	559.0s
PR Sous Chef	1,865	8	476.5s
Package Specification Extractor	1,711	1	633.0s

---

Trending Indicators

• 7-day API trend: ↓ −35.4% vs. previous 7 days
• 30-day API trend: → (insufficient data — 16 days of history; ~60 needed)
• GitHub REST API call rate: ~36,898 calls/day over last 7 days (hourly limit: 15,000)

---

📦 Cache Memory Status

• Location: /tmp/gh-aw/cache-memory/trending/api-consumption/history.jsonl
• Cache restored from previous run: yes (15 entries)
• Collection mode: incremental (history already held 15 consecutive days — older days are already computed, so a full 90-day backfill was unnecessary; only today's data point was collected)
• Logs start_date used: -1d
• Data points stored: 16
• Earliest entry: 2026-05-18
• Retention policy: 90 days

i️ Collection Notes

• The logs download timed out at the MCP bridge layer (120s HTTP cap) but the server continued writing run directories; the dataset was polled until stable at 157 completed runs dated 2026-06-03 before aggregating.
• REST API consumption is read from github_rate_limit_usage.core_consumed in each run's run_summary.json. Safe-output writes are counted from safeoutputs.jsonl write-type actions (excludes noop/missing_*).

---

Automatically generated by the api-consumption-report workflow.

Generated by 📊 GitHub API Consumption Report Agent · opus48 11.9M · ◷

• expires on Jun 6, 2026, 12:33 PM UTC