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

[github-actions[bot]]

📊 GitHub API Consumption Report

Report Date: 2026-07-01 · Repository: github/gh-aw · Run: #28514882817

---

Today at a Glance

Metric	Value
🤖 Total Runs	94 (77 ✅ / 17 ❌)
🎯 Success Rate	81.9%
🔗 GitHub REST API Calls	44,316 (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	691s (p95: 1,244s)

⚠️ Partial dataset. The logs tool hit the 60s bridge deadline on the initial call and both retries; 94 of ~202 attempted run directories were fully downloaded. Metrics cover the collection window 06:08 → 11:37 UTC (~5.5h of 2026-07-01), not a full 24h. Treat totals and trends as a lower-bound sample.

---

🔗 GitHub API Calls Trend (90 days)

Daily REST API consumption is highly volatile because each day's collection window is partial and inconsistent — values swing from <1k to >85k. One clear anomaly stands out: 2026-06-17 at ~574k calls (>2σ), driven by a 391-run day. Today's 44,316 sits below the 7-day rolling average (~56.6k), but that comparison is skewed by today's truncated ~5.5h window.

---

🔗 GitHub API Calls by Workflow Trend (30 days)

The heaviest recurring consumers are the review/gate family — Test Quality Sentinel, Matt Pocock Skills Reviewer, Design Decision Gate, and PR Sous Chef — which reappear near the top of the per-workflow ranking day after day. Smoke CI is a consistent baseline consumer given its scheduled cadence. No single workflow dominates the 30-day picture; consumption is spread across the reviewer cohort.

---

🔗 GitHub REST API Calls Heatmap (90 days)

The heatmap aggregates core quota by weekday × ISO week. The mid-June week carries the darkest cell (the 574k 2026-06-17 spike), while most weekday cells cluster in the low-tens-of-thousands. Weekend cells are noticeably lighter, consistent with fewer PR-triggered agentic runs on Saturdays and Sundays.

---

🍩 Top API Burners (24h)

Consumption in the collected window is evenly distributed, not concentrated: the top 3 workflows account for just 38.9% of the 44,316 total, and the top 6 each land between ~5,160 and ~5,955 calls. This flat profile means there's no single runaway workflow to target — optimisation gains would come from trimming the whole reviewer cohort rather than one outlier.

---

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

The top consumer — Design Decision Gate at 5,955 calls across 6 runs — reaches only 39.7% of the 15,000/hr core limit, and every other workflow sits well below it. No workflow is anywhere near rate-limit risk in this window. The clearest optimisation lever is the cluster of six reviewer/gate workflows each burning ~1,000 calls/run; caching repository metadata or batching GraphQL reads across those runs would compound across the fleet.

---

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

Workflow	REST API Calls	Runs	Avg Duration
Design Decision Gate 🏗️	5,955	6	7m 28s
Impeccable Skills Reviewer	5,693	6	13m 14s
Smoke CI	5,583	5	4m 23s
Matt Pocock Skills Reviewer	5,505	6	12m 13s
Test Quality Sentinel	5,382	6	8m 58s
PR Code Quality Reviewer	5,161	6	10m 05s
Smoke Copilot Sub Agents	2,186	1	6m 53s
PR Sous Chef	1,802	4	8m 57s
PR Description Updater	1,101	2	9m 29s
Contribution Check	1,011	2	23m 27s

---

Trending Indicators

• 7-day API trend: ↓ 37.7% vs. previous 7 days (56.6k/day vs 90.9k/day — heavily influenced by inconsistent partial collection windows; interpret with caution)
• 30-day API trend: → (insufficient data — need 60 non-null daily points, only 42 available)
• GitHub REST API call rate: ~56,605 calls/day over the last 7 days (hourly limit: 15,000; observed per-workflow-per-window peak was 5,955)

---

📦 Cache Memory Status

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

🔎 Collection Diagnostics

• Initial logs(start_date="-1d") call + 2 retries each hit the 60s bridge context deadline exceeded.
• Downloaded run dirs accumulate on disk across calls: 50 → 94 full dirs (with aw_info.json + run_summary.json); 202 total dirs attempted.
• Continuation retries exhausted; proceeded with the 94-run partial dataset as instructed.
• Safe-output writes derived from run_summary.run.SafeItemsCount (no safe_output.jsonl present); all collected runs reported 0 safe items — dominated by smoke/CI runs.

---

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 · 207.5 AIC · ⌖ 33.7 AIC · ⊞ 11.8K · ◷

• expires on Jul 4, 2026, 3:56 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 #42942.