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

[github-actions[bot]]

📊 GitHub API Consumption Report

Report Date: 2026-06-13 · Repository: github/gh-aw · Run: #27465379625

---

Today at a Glance

Metric	Value
🤖 Total Runs	122 (100 ✅ / 16 ❌)
🎯 Success Rate	82.0%
🔗 GitHub REST API Calls	78,479 (core quota consumed — includes reads, writes, and all GitHub API operations)
📝 Safe-Output Writes	6 (issues + PRs + comments + discussions created by safe-output tools)
⏱ Avg Duration	393s (p95: 1226s)

---

🔗 GitHub API Calls Trend (90 days)

Daily REST API consumption is volatile, ranging from ~7.5k on quiet days (06-12) to a 207.9k spike on 06-09. Today's 78,479 calls sit well above the recent low and lift the 7-day rolling average back toward the ~67k/day band. The peak on 06-09 remains the clear outlier driven by an unusually heavy run volume (187 runs).

---

🔗 GitHub API Calls by Workflow Trend (30 days)

Smoke CI, Design Decision Gate 🏗️, and Matt Pocock Skills Reviewer are the most persistent top consumers across the window. Smoke CI scales with PR activity (21 runs today), while Design Decision Gate burns a high per-run rate on relatively few runs. Most other workflows stay in the low-hundreds band, so quota pressure is concentrated in a small set of CI/review workflows.

---

🔗 GitHub REST API Calls Heatmap (90 days)

Consumption clusters on weekdays, mirroring PR and review traffic, with noticeably lighter weekend cells. The hottest cell corresponds to the 06-09 spike. Day-to-day variance within a week is high, signalling that demand is event-driven (PR bursts) rather than a steady background load.

---

🍩 Top API Burners (24h)

The top three workflows — Smoke CI (29%), Design Decision Gate 🏗️, and Matt Pocock Skills Reviewer — together account for roughly 72% of all REST API quota consumed today. This concentration means optimisation effort on just a few workflows would yield the largest savings, but it also represents a concentration risk if any one of them regresses into a tight API loop.

---

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

Smoke CI (22,516) and Design Decision Gate 🏗️ (21,664) dominate, the latter averaging ~3.6k calls per run — a strong candidate for caching or request-batching review. No single run breached the 15,000 calls/hour core limit, but Design Decision Gate's per-run intensity is worth watching. Lower-volume review workflows are efficient and need no action.

---

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

Workflow	REST API Calls	Runs	Avg Duration
Smoke CI	22,516	21	109s
Design Decision Gate 🏗️	21,664	6	334s
Matt Pocock Skills Reviewer	12,309	6	296s
PR Code Quality Reviewer	6,470	6	410s
PR Sous Chef	6,108	6	504s
Test Quality Sentinel	5,617	6	234s
PR Description Updater	2,045	3	376s
Contribution Check	410	2	562s
Sub-Issue Closer	292	1	551s
Issue Monster	250	5	309s

---

Trending Indicators

• 7-day API trend: ↑ +45.0% vs. previous 7 days
• 30-day API trend: → (insufficient data — 26 days of history; needs 60)
• GitHub REST API call rate: ~66,982 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 (25 entries)
• Collection mode: incremental (history rich enough; 90-day backfill timed out at the MCP layer, fell back to -2d)
• Logs start_date used: -2d
• Data points stored: 26
• Earliest entry: 2026-05-18
• Retention policy: 90 days

---

Automatically generated by the api-consumption-report workflow.

Generated by 📊 GitHub API Consumption Report Agent · 210 AIC · ⌖ 18.3 AIC · ⊞ 12.1K · ◷

• expires on Jun 16, 2026, 3:38 AM UTC-08:00

[github-actions[bot]]

This discussion has been marked as outdated by GitHub API Consumption Report Agent.

A newer discussion is available at Discussion #39215.