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

[github-actions[bot]]

📊 GitHub API Consumption Report

Report Date: 2026-07-02 · Repository: github/gh-aw · Run: #28586712992

⚠️ Partial dataset: The logs() collector hit the 60s bridge deadline on the initial call and both retries. 84 of ~175 attempted run directories were fully downloaded, covering roughly the 05:10–11:23 UTC window of 2026-07-02. Absolute totals below under-count the true 24h figures; treat them as a lower bound. Prior days (06-30, 07-01) were similarly partial, so day-over-day comparisons are noisy.

---

Today at a Glance

Metric	Value
🤖 Total Runs	84 (65 ✅ / 19 ❌)
🎯 Success Rate	77.4%
🔗 GitHub REST API Calls	27,495 (core quota consumed — includes reads, writes, and all GitHub API operations)
📝 Safe-Output Writes	0 (issues + PRs + comments + discussions created by safe-output tools; source: run_summary.run.SafeItemsCount)
⏱ Avg Duration	672s (p95: 1255s)

---

🔗 GitHub API Calls Trend (90 days)

Total REST API consumption has run in the tens-of-thousands per day since the tracking window opened, with a standout spike on 2026-06-17 (~574K). The 7-day rolling average sits near 48K calls/day, though several recent days (06-30, 07-01, 07-02) reflect partial log collection and therefore dip below the true totals.

---

🔗 GitHub API Calls by Workflow Trend (30 days)

The PR-review family — Test Quality Sentinel, Matt Pocock Skills Reviewer, Design Decision Gate, Impeccable Skills Reviewer, and PR Code Quality Reviewer — consistently tops per-workflow consumption. These reviewers fire on PR activity and each burns a few thousand core-quota calls per day, tracking well above the 30-day average total line.

---

🔗 GitHub REST API Calls Heatmap (90 days)

The heatmap shows sustained weekday activity through mid/late June, with the darkest cells clustering around 06-24 to 06-29 (peak days of 70K–88K calls). The lighter recent cells for 06-30 and 07-02 are collection artifacts (partial windows) rather than a genuine drop in activity.

---

🍩 Top API Burners (24h)

Consumption is moderately concentrated: the top five PR-review workflows together account for roughly 70% of the captured 24h REST API calls. No single workflow dominates outright — the leader, Test Quality Sentinel, is ~21% of the total — so there is no single runaway consumer, but the reviewer cluster as a whole is the clear cost center.

---

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

The top consumer (Test Quality Sentinel, 5,791 calls) sits comfortably under the 15,000/hr core limit, and no captured workflow approaches it. The optimization opportunity is in the PR-review cluster: five reviewers each run per PR and collectively drive most consumption — deduplicating overlapping GitHub reads across them (shared PR/file fetches) would cut the largest slice.

---

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

Workflow	REST API Calls	Runs	Avg Duration
Test Quality Sentinel	5,791	4	548s
Matt Pocock Skills Reviewer	4,265	4	874s
Design Decision Gate 🏗️	3,973	4	463s
Impeccable Skills Reviewer	2,837	4	723s
PR Code Quality Reviewer	2,542	4	637s
Smoke CI	2,328	9	238s
PR Description Updater	1,878	3	534s
PR Sous Chef	1,298	5	557s
Contribution Check	1,203	2	1194s
AI Moderator	991	2	1165s

---

Trending Indicators

• 7-day API trend: ↑ +129.4% vs. previous 7 days (inflated by partial-collection days; interpret with caution)
• 30-day API trend: → (insufficient data — 44 of the 60 days needed for a full 30-vs-30 comparison)
• GitHub REST API call rate: ~48,011 calls/day over last 7 days (hourly limit: 15,000 — per-run consumption stays well under this)

---

📦 Cache Memory Status

• Location: /tmp/gh-aw/cache-memory/trending/api-consumption/history.jsonl
• Cache restored from previous run: yes (43 existing entries)
• Collection mode: incremental
• Logs start_date used: -1d
• Data points stored: 44
• 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 · 196.6 AIC · ⌖ 48 AIC · ⊞ 11.8K · ◷

• expires on Jul 5, 2026, 3:49 AM UTC-08:00