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

[github-actions[bot]]

📊 GitHub API Consumption Report

Report Date: 2026-07-04 · Repository: github/gh-aw · Run: #28704332984

⚠️ Collection note: Today's window captured 300 runs spanning ~19h (07-03 15:59 → 07-04 11:05 UTC) after the 2-continuation limit was reached and the earliest ~4.75h page (07-03 11:13–15:59) was not fetched. This is a much more complete capture than recent single-batch days (~60–84 runs, ~4–6h), so absolute totals and short-term trends below read higher than prior entries largely due to broader coverage, not purely organic growth.

---

Today at a Glance

Metric	Value
🤖 Total Runs	300 (230 ✅ / 70 ❌)
🎯 Success Rate	76.7%
🔗 GitHub REST API Calls	182,812 (core quota consumed — includes reads, writes, and all GitHub API operations)
📝 Safe-Output Writes	0 (issues + PRs + comments + discussions created by safe-output tools)
⏱ Avg Duration	616.1s (p95: 1158.0s)

---

🔗 GitHub API Calls Trend (90 days)

Daily core-quota consumption trends upward across the 90-day window, with the 07-04 bar (182,812) standing well above the 7-day rolling average — this peak is driven mostly by today's fuller collection window rather than a genuine per-run spike. Setting the coverage artifact aside, per-run consumption (~609 core/run) remains in line with recent days, and the 30-day rolling line stays comparatively flat.

---

🔗 GitHub API Calls by Workflow Trend (30 days)

The reviewer-class workflows — PR Code Quality Reviewer, Matt Pocock Skills Reviewer, Test Quality Sentinel, and Impeccable Skills Reviewer — consistently sit at the top of daily quota consumption over the last 30 days. Design Decision Gate and Smoke CI round out the leading cohort, with the whole group climbing on 07-04 in lockstep with the broader capture window.

---

🔗 GitHub REST API Calls Heatmap (90 days)

Weekday cells are consistently darker than weekends, reflecting API load that tracks active PR review during the work week. The most recent week's Friday cell is the hottest in the map — again a function of today's deeper collection — while earlier weeks show a steadier, lower-intensity Monday–Friday band.

---

🍩 Top API Burners (24h)

The top six reviewer/CI workflows each consume 19k–25k core quota and together account for the large majority of the day's 182,812 total. Consumption is fairly evenly spread across those six (no single workflow exceeds ~14% of the total), so concentration risk is moderate — the load is broad rather than dominated by one runaway workflow.

---

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

PR Code Quality Reviewer (24,992) and Matt Pocock Skills Reviewer (22,245) lead consumption, each across 23 runs. No individual run approaches the 15,000/hr core limit, but the reviewer workflows' high per-run averages (~1,000+ core/run) make them the prime candidates for optimisation — caching repeated repo/PR reads or batching API queries would meaningfully cut the aggregate footprint.

---

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

Workflow	REST API Calls	Runs	Avg Duration
PR Code Quality Reviewer	24,992	23	16.3m
Matt Pocock Skills Reviewer	22,245	23	13.0m
Test Quality Sentinel	21,207	23	9.0m
Smoke CI	20,429	23	3.0m
Design Decision Gate 🏗️	19,641	23	6.8m
Impeccable Skills Reviewer	19,402	23	12.1m
PR Description Updater	14,403	8	7.8m
PR Sous Chef	12,617	28	6.0m
Smoke Copilot - AOAI (apikey)	3,428	2	13.1m
Smoke Copilot	3,002	2	13.0m

---

Trending Indicators

• 7-day API trend: ↑ +52.8% vs. previous 7 days (inflated by today's broader collection window — treat as an upper bound)
• 30-day API trend: → (insufficient data — need 60 days of history; currently 46 points)
• GitHub REST API call rate: ~57,983 core quota/day over last 7 days (hourly limit: 15,000 core/hr per run)

---

📦 Cache Memory Status

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

i️ Data completeness & method

• REST API metric: github_rate_limit_usage.core_consumed summed per run from each run's run_summary.json (actual quota consumed, not raw request count).
• Safe-output writes: run_summary.run.SafeItemsCount — reported 0 across all 300 runs in the window (consistent with prior history entries).
• Pagination: 3 of an available 4 pages retrieved (300 runs). The 2-continuation limit was reached; two continuation calls each timed out once and succeeded on a single retry. The 4th page (07-03 11:13–15:59) was intentionally not fetched, so the window is partial (~19h of 24h).

---

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 · 232.4 AIC · ⌖ 38.3 AIC · ⊞ 11.9K · ◷

• expires on Jul 7, 2026, 3:40 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 #43533.