[api-consumption] 📊 GitHub API Consumption Report — 2026-07-19

[github-actions[bot]]

📊 GitHub API Consumption Report

Report Date: 2026-07-19 · Repository: github/gh-aw · Run: #29684490719

---

Today at a Glance

Metric	Value
🤖 Total Runs	134 (129 ✅ / 5 ❌)
🎯 Success Rate	96.3%
🔗 GitHub REST API Calls	87,642 (core quota consumed — includes reads, writes, and all GitHub API operations)
📝 Safe-Output Writes	n/a (⚠️ authoritative safe_items_count field absent from all run summaries in this dataset — see note below)
⏱ Avg Duration	654.6s (p95: 1176.0s)

⚠️ Data note: The authoritative safe-output actuation field (run.safe_items_count) was not populated in any of the 134 run_summary.json files collected today, so safe-output writes could not be measured (for reference, yesterday recorded 233). Additionally, the logs MCP call returned an HTTP timeout after paging; 134 runs with complete summaries were recovered from disk (138 empty run directories were skipped). The run count is in line with recent days (~131 yesterday), so REST API totals are considered representative, but the dataset may be marginally partial.

---

🔗 GitHub API Calls Trend (90 days)

Total REST API consumption today was 87.6K, close to the 7-day rolling average (~114K/day). The series is spiky: a standout peak of 574K on 2026-06-17 and a secondary 276K spike on 2026-07-15 punctuate an otherwise 50K–110K baseline. The 7-day rolling average has been climbing steadily since early July.

---

🔗 GitHub API Calls by Workflow Trend (30 days)

The PR-review family — PR Code Quality Reviewer, Matt Pocock Skills Reviewer, and Impeccable Skills Reviewer — are the consistent top consumers over the last 30 days, each running ~10–13 times per day. Their per-day API footprint tracks PR activity closely, so consumption rises on high-PR days and largely explains the recent upward drift.

---

🔗 GitHub REST API Calls Heatmap (90 days)

The heatmap shows consumption concentrated on weekdays, with weekends noticeably lighter — consistent with PR-driven review workflows. The mid-June cell (2026-06-17) is the darkest by a wide margin, marking the 574K anomaly, with a lesser hotspot in mid-July.

---

🍩 Top API Burners (24h)

Consumption is highly concentrated: the four review/gate workflows (PR Code Quality, Matt Pocock, Impeccable Skills, Design Decision Gate) together burn ~58.5K calls — roughly 67% of today's total. This concentration means optimisation effort on the review family would yield the largest quota savings.

---

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

PR Code Quality Reviewer leads at 16.3K aggregate calls across 13 runs (~1.25K/run). No individual run approaches the 15,000/hour REST limit — the 15k line reflects the hourly quota, whereas these are daily aggregates over many runs. The lighter, per-run reviewers are efficient; the biggest lever is reducing redundant reads within the top review workflows (e.g. caching PR/file metadata across steps).

---

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

Workflow	REST API Calls	Runs	Avg Duration
PR Code Quality Reviewer	16,257	13	614.2s
Matt Pocock Skills Reviewer	15,207	13	579.1s
Impeccable Skills Reviewer	14,690	13	519.2s
Design Decision Gate 🏗️	12,325	13	510.3s
Test Quality Sentinel	6,748	13	543.9s
PR Description Updater	5,312	6	513.2s
PR Sous Chef	4,913	8	652.6s
Tidy	2,511	2	958.0s
Visual Regression Checker	2,378	2	1002.0s
Auto-Triage Issues	1,358	1	646.0s

---

Trending Indicators

• 7-day API trend: ↑ +42.2% vs. previous 7 days (inflated by the 2026-07-15 spike of 276K)
• 30-day API trend: → +3.4% vs. prior 30 days (essentially flat)
• GitHub REST API call rate: ~114,283 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 (59 entries)
• Collection mode: incremental
• Logs start_date used: -1d
• Data points stored: 60
• Earliest entry: 2026-05-18
• Retention policy: 90 days

---

Automatically generated by the api-consumption-report workflow.

Warning

Firewall blocked 1 domain

The following domain was blocked by the firewall during workflow execution:

• awmgmcpg

To allow these domains, add them to the network.allowed list in your workflow frontmatter:

network:
  allowed:
    - defaults
    - "awmgmcpg"

See Network Configuration for more information.

Generated by 📊 GitHub API Consumption Report Agent · 257.4 AIC · ⌖ 40.6 AIC · ⊞ 12.1K · ◷

• expires on Jul 22, 2026, 3:28 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 #46808.