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

[github-actions[bot]]

📊 GitHub API Consumption Report

Report Date: 2026-06-08 · Repository: github/gh-aw · Run: #27136923413

⏱️ Snapshot note: this report was generated mid-day (UTC), so the 2026-06-08 figures below reflect a partial day. Even so, today's REST API consumption (80,144) has already more than doubled 2026-06-07's full-day total (36,520).

---

Today at a Glance

Metric	Value
🤖 Total Runs	197 (159 ✅ / 35 ❌)
🎯 Success Rate	80.7%
🔗 GitHub REST API Calls	80,144 (core quota consumed — includes reads, writes, and all GitHub API operations)
📝 Safe-Output Writes	195 (issues + PRs + comments + discussions created by safe-output tools)
⏱ Avg Duration	520s (p95: 1281s)

---

🔗 GitHub API Calls Trend (90 days)

Daily REST API consumption has been volatile, swinging between a low of 17,043 (2026-06-02) and a sharp peak of 118,077 on 2026-05-27. The 7-day rolling average has held remarkably steady in the 40k–55k band throughout the window, smoothing out day-to-day spikes. Today's partial-day reading of 80,144 is already pushing the rolling average back up toward the high end of that band.

---

🔗 GitHub API Calls by Workflow Trend (30 days)

The top API consumers are consistently the PR-triggered review workflows — PR Code Quality Reviewer, Test Quality Sentinel, Matt Pocock Skills Reviewer, and Design Decision Gate — each running ~9 times per day and burning 6k–10k core quota apiece. Smoke CI has emerged as the new top burner today, scaling to 30 runs as PR activity surged. These five workflows alone account for the majority of the repository's REST API footprint on any given day.

---

🔗 GitHub REST API Calls Heatmap (90 days)

The heatmap shows consumption concentrated on weekdays, tracking developer PR activity, with the mid-to-late-May spike (ISO week containing 2026-05-27) standing out as the single hottest cell. Weekend cells are markedly cooler, consistent with scheduled-only workflow activity when human-triggered PR reviews quiet down. No anomalous off-hours bursts are visible — the pattern is healthy and predictable.

---

🍩 Top API Burners (24h)

Consumption is moderately concentrated: Smoke CI alone accounts for 25.9% of today's quota (20,795 calls across 30 runs), and the top three workflows together make up roughly half of all REST API usage. The long tail of 86 other workflows contributes just 9.8% combined. This concentration means optimisation effort is best focused on the handful of high-frequency review and CI workflows rather than the many one-off scheduled jobs.

---

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

The top consumers are Smoke CI (20,795), PR Code Quality Reviewer (10,533), and Matt Pocock Skills Reviewer (8,703). All individual workflow runs remain comfortably below the 15,000/hr core limit — the dashed red line is never crossed by a single run. Smoke CI's aggregate is driven by run count (30×) rather than per-run intensity, so the most effective optimisation lever would be deduplicating or debouncing Smoke CI triggers rather than trimming any single workflow's API calls.

---

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

Workflow	REST API Calls	Runs	Avg Duration
Smoke CI	20,795	30	144s
PR Code Quality Reviewer	10,533	9	899s
Matt Pocock Skills Reviewer	8,703	9	634s
Test Quality Sentinel	8,208	9	509s
Design Decision Gate 🏗️	7,554	9	354s
PR Description Updater	6,375	6	371s
Workflow Health Manager - Meta-Orchestrator	5,338	1	850s
PR Sous Chef	4,814	8	468s
Auto-Triage Issues	2,436	7	202s
AI Moderator	1,706	8	769s

---

Trending Indicators

• 7-day API trend: ↑ +11.7% vs. previous 7 days
• 30-day API trend: → insufficient data (only 21 days of history collected so far; 30-day comparison needs 60)
• GitHub REST API call rate: ~52,921 calls/day over last 7 days (hourly limit: 15,000)

⚠️ Run health watch: today's success rate (80.7%, 35 failures) is well below the recent ~95% baseline. Some of this is the partial-day window catching in-flight runs, but the elevated failure count is worth monitoring on tomorrow's full-day report.

---

📦 Cache Memory Status

• Location: /tmp/gh-aw/cache-memory/trending/api-consumption/history.jsonl
• Cache restored from previous run: yes (20 entries)
• Collection mode: backfill (entry count 20 < 30 threshold)
• Logs start_date used: -90d (only current-day runs were returned within the fetch window; prior days came from cached history)
• Data points stored: 21
• Earliest entry: 2026-05-18
• Retention policy: 90 days

---

Automatically generated by the api-consumption-report workflow.

Generated by 📊 GitHub API Consumption Report Agent · 234.3 AIC · ⌖ 35.1 AIC · ⊞ 12.2K · ◷

• expires on Jun 11, 2026, 4:32 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 #38103.