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

[github-actions[bot]]

📊 GitHub API Consumption Report

Report Date: 2026-07-22 · Repository: github/gh-aw · Run: #29915450088

---

Today at a Glance

Metric	Value
🤖 Total Runs	209 (204 ✅ / 5 ❌)
🎯 Success Rate	97.6%
🔗 GitHub REST API Calls	106,380 (core quota consumed — includes reads, writes, and all GitHub API operations)
📝 Safe-Output Writes	N/A this window — safe_output.jsonl / run.safe_items_count were absent from the collected logs. Proxy: the safe_outputs actuation job completed successfully in 207 / 209 runs.
⏱ Avg Duration	553.7s (p95: 1039.4s)

i️ Data note: This collection window's run directories did not include the safe-output actuation files, so per-item write counts could not be computed today. The authoritative REST API quota metric (github_rate_limit_usage.core_consumed) was fully available for all 209 runs.

---

🔗 GitHub API Calls Trend (90 days)

Daily REST API consumption has been steady in the 85k–106k band for the past week. Today's 106,380 is the 8th-highest day in the 63-day record and the week's peak, nudging the 7-day average up. The lone historical outlier remains the 574k spike on 2026-06-17; nothing in the recent window approaches that, and no >2σ anomalies were flagged for the last 90 days.

---

🔗 GitHub API Calls by Workflow Trend (30 days)

The PR-facing reviewers — PR Code Quality Reviewer, Impeccable / Matt Pocock Skills Reviewer, Test Quality Sentinel, and Design Decision Gate — consistently dominate quota over the trailing 30 days, each scaling with PR volume (17–20 runs/day). Their per-day consumption moves together, signalling PR activity is the primary driver of the repo's API footprint rather than any single runaway workflow.

---

🔗 GitHub REST API Calls Heatmap (90 days)

Weekday cells burn hottest, tracking PR-review and CI-driven workflows during active development; weekends cool noticeably as scheduled-only workflows carry the load. The single darkest cell corresponds to the mid-June spike week; recent weeks show an even, moderate intensity with no alarming concentration.

---

🍩 Top API Burners (24h)

The top six workflows account for roughly 75% of today's quota, with the three skills/quality reviewers alone near 40%. Consumption is broadly distributed across ~70 workflows rather than concentrated in one, so no single workflow poses a quota-exhaustion risk — the aggregate is what to watch.

---

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

Top consumers are PR Code Quality Reviewer (14,663), Impeccable Skills Reviewer (14,621), and Matt Pocock Skills Reviewer (14,062) — each spread across 18 runs, so per-run consumption (~800/run) stays well under the 15,000/hr limit. The clearest optimisation lever is the three near-identical skills-reviewer workflows: consolidating shared GitHub reads (PR files, diffs) across them could trim ~10k quota/day.

---

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

Workflow	REST API Calls	Runs	Avg Duration
PR Code Quality Reviewer	14,663	18	581.7s
Impeccable Skills Reviewer	14,621	18	418.9s
Matt Pocock Skills Reviewer	14,062	18	497.2s
Test Quality Sentinel	13,581	20	440.8s
Design Decision Gate 🏗️	13,142	18	400.5s
PR Description Updater	12,494	8	364.8s
Tidy	7,191	8	711.0s
jsweep - JavaScript Unbloater	4,945	1	1150.0s
Scout	2,503	1	422.0s
PR Sous Chef	2,256	11	613.1s

---

Trending Indicators

• 7-day API trend: ↓ -15.0% vs. previous 7 days
• 30-day API trend: ↑ +22.8% vs. prior 30 days
• GitHub REST API call rate: ~93,411 calls/day over last 7 days (hourly limit: 15,000 — daily avg ≈ 3,892/hr, comfortably within budget)

---

📦 Cache Memory Status

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

• expires on Jul 25, 2026, 3:41 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 #47556.