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

[github-actions[bot]]

📊 GitHub API Consumption Report

Report Date: 2026-07-06 · Repository: github/gh-aw · Run: #28790013719

⚠️ Partial window: the incremental -1d collection returned runs from 06:38–11:53 UTC today (the initial logs call timed out during response formatting; the 103 run directories already written to disk were used as the authoritative dataset, and no continuation was attempted). Figures below reflect that ~5-hour slice, not a full 24h.

---

Today at a Glance

Metric	Value
🤖 Total Runs	103 (87 ✅ / 16 ❌)
🎯 Success Rate	84.5%
🔗 GitHub REST API Calls	40,605 (core quota consumed — includes reads, writes, and all GitHub API operations)
📝 Safe-Output Writes	183 (issues + PRs + comments + discussions created by safe-output tools)
⏱ Avg Duration	715s (p95: 1514s)

---

🔗 GitHub API Calls Trend (90 days)

Daily REST API consumption has held a stable ~50–70k baseline across the 90-day window, with the 30-day rolling average drifting gently upward to ~63k/day. The dominant feature is a single >2σ anomaly on ~Jun 16 (≈570k calls) — roughly 10× the baseline — likely a one-off backfill or runaway workflow. Today's partial reading of 40.6k sits below the recent 7-day mean, consistent with only ~5 hours of runs having been captured.

---

🔗 GitHub API Calls by Workflow Trend (30 days)

The PR-review family — PR Code Quality Reviewer, Impeccable Skills Reviewer, Test Quality Sentinel, and Matt Pocock Skills Reviewer — consistently anchors the top of the stack, together accounting for the bulk of day-to-day quota. Design Decision Gate and Smoke CI are steady secondary consumers. No new workflow has emerged as a runaway consumer over the last 30 days; the mix is stable.

---

🔗 GitHub REST API Calls Heatmap (90 days)

Consumption concentrates on weekdays, mirroring PR and CI activity, with weekends noticeably lighter. The mid-June week carries the standout hotspot driven by the single-day anomaly. Otherwise weekly intensity is fairly even, with no persistent day-of-week runaway pattern beyond the expected weekday tilt.

---

🍩 Top API Burners (24h)

The four PR/skills reviewers plus Design Decision Gate consume roughly 80% of today's REST API quota, a meaningful concentration in the review-automation cluster. Individually none approaches the hourly ceiling, but their combined per-PR footprint is the single largest lever for reducing total consumption.

---

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

Top consumer PR Code Quality Reviewer used 8,070 calls across 9 runs (~900/run); no single workflow came close to the 15,000/hr limit (dashed line). The heaviest per-run cost belongs to reviewers making many file/PR reads — batching GraphQL reads or caching PR metadata across steps is the clearest optimisation opportunity. Daily yamllint Fixer stands out for duration (2,189s for 1,479 calls) rather than volume.

---

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

Workflow	REST API Calls	Runs	Avg Duration
PR Code Quality Reviewer	8,070	9	957s
Impeccable Skills Reviewer	7,582	10	761s
Test Quality Sentinel	6,097	9	532s
Matt Pocock Skills Reviewer	5,721	9	815s
Design Decision Gate	5,177	10	402s
Smoke CI	2,816	6	195s
Daily yamllint Fixer	1,479	1	2189s
PR Sous Chef	1,234	3	491s
Auto-Triage Issues	1,105	1	427s
AI Moderator	366	1	1179s

---

Trending Indicators

• 7-day API trend: ↑ +16.5% vs. previous 7 days
• 30-day API trend: → (insufficient data — need 60 days; 48 collected)
• GitHub REST API call rate: ~63,512 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 (47 entries)
• Collection mode: incremental
• Logs start_date used: -1d
• Data points stored: 48
• Earliest entry: 2026-05-18
• Retention policy: 90 days

⚙️ Run health & collection notes

• Runs analysed: 103 (all reported core_consumed via response-header deltas)
• Failures: 16 runs concluded failure (84.5% success rate)
• Safe-output writes breakdown: comments/reviews dominate (PR review comments 64, comments 39, submit review 28), plus 21 issues, 10 discussions, 7 PRs created
• Data caveat: single partial collection window (~5h); the initial logs call timed out during formatting but 103 run directories were already on disk and used as the authoritative dataset. No continuation calls were made.

---

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.1 AIC · ⌖ 61.6 AIC · ⊞ 11.9K · ◷

• expires on Jul 9, 2026, 4:19 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 #44014.