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

[github-actions[bot]]

📊 GitHub API Consumption Report

Report Date: 2026-07-14 · Repository: github/gh-aw · Run: #29328025217

---

Today at a Glance

Metric	Value
🤖 Total Runs	101 (84 ✅ / 17 ❌)
🎯 Success Rate	83.2%
🔗 GitHub REST API Calls	73,380 (core quota consumed — includes reads, writes, and all GitHub API operations)
📝 Safe-Output Writes	61 (issues + PRs + comments + discussions created by safe-output tools)
⏱ Avg Duration	595.2s (p95: 1369.0s)

⚠️ Partial dataset: the logs collection call reached its transport timeout mid-download, so this report covers the 101 runs whose logs finished downloading to disk (all dated 2026-07-14). Some additional runs from the last 24h may be missing; totals should be read as a lower bound.

---

🔗 GitHub API Calls Trend (90 days)

REST API consumption has climbed over the past week (↑ +22.0% vs. the prior 7 days), settling in a busy 70k–160k calls/day band since early July. The single dominant feature of the 90-day window is a 574,243-call spike on Jun 17 — the only point beyond 2σ and roughly 8× the current daily average — which reads as a runaway or one-off backfill event worth a retrospective look. Outside that spike, daily volume oscillates between near-idle weekends and 100k+ weekday peaks.

---

🔗 GitHub API Calls by Workflow Trend (30 days)

Over the last 30 days the load is spread across the review-and-smoke fleet rather than owned by one runaway workflow. Smoke CI stays near the top thanks to its high run frequency, while the PR reviewers (Code Quality, Description Updater), the skills reviewers, and the security scan trade places day to day. No single workflow shows a sustained breakaway growth curve — the aggregate rise is broad-based.

---

🔗 GitHub REST API Calls Heatmap (90 days)

The heatmap is weekday-dominant: mid-week cells consistently outweigh weekends, matching PR-driven automation. The mid-June week carries the Jun 17 anomaly, whose intensity dwarfs every other cell on the scale. The most recent weeks show a broad warm band across Mon–Fri, confirming the current elevated-but-stable regime.

---

🍩 Top API Burners (24h)

Smoke CI alone drives 20.7% of the last 24h of REST calls, and the top 3 workflows (Smoke CI, Impeccable Skills Reviewer, Sighthound Security Scan) together account for 42.2% of consumption. That's a moderate concentration — no workflow monopolises quota, but the smoke-and-review cluster is where any optimisation effort will pay off most.

---

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

Smoke CI leads at 15,175 calls across 13 runs (~1.2k/run), followed by the skills reviewers and the security scan in the 7–8k range. Crucially, no individual run approaches the 15,000/hour per-token limit — the daily aggregate is spread across many independent runs, so the dashed limit line is a reference, not a breach. Smoke CI's combination of high run count and per-run footprint makes it the clearest candidate for call-count reduction (e.g. caching repo-content reads).

---

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

Workflow	REST API Calls	Runs	Avg Duration
Smoke CI	15,175	13	4m 44s
Impeccable Skills Reviewer	8,250	7	7m 28s
Sighthound Security Scan	7,570	7	13m 13s
Design Decision Gate 🏗️	6,790	7	7m 11s
PR Code Quality Reviewer	6,318	7	8m 50s
PR Sous Chef	5,896	5	8m 3s
Matt Pocock Skills Reviewer	5,774	6	8m 11s
PR Description Updater	5,697	7	8m 12s
Test Quality Sentinel	5,154	7	8m 44s
Tidy	3,191	4	10m 18s

---

Trending Indicators

• 7-day API trend: ↑ +22.0% vs. previous 7 days
• 30-day API trend: → (insufficient data — 55 days of history; a 30-day-vs-prior-30-day comparison needs 60)
• GitHub REST API call rate: ~77,478 calls/day over last 7 days (per-token hourly limit: 15,000 — the daily figure spans many runs/tokens and is not a single-bucket measure)

---

📦 Cache Memory Status

• Location: /tmp/gh-aw/cache-memory/trending/api-consumption/history.jsonl
• Cache restored from previous run: yes (54 entries)
• Collection mode: incremental
• Logs start_date used: -1d
• Data points stored: 55
• Earliest entry: 2026-05-18
• Retention policy: 90 days

🧾 Safe-Output Writes — full breakdown (24h)

Counted toward the headline (issues + PRs + comments + discussions): 61

• add_comment: 34
• create_issue: 16
• create_pull_request: 6
• create_discussion: 5

Other safe-output activity (not counted in the headline): submit_pull_request_review 23, create_pull_request_review_comment 22, assign_to_agent 12, update_pull_request 6, add_labels 1, push_to_pull_request_branch 1, comment_memory 1.

---

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 · 284.7 AIC · ⌖ 51.3 AIC · ⊞ 11.9K · ◷

• expires on Jul 17, 2026, 3:36 AM UTC-08:00