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

[github-actions[bot]]

📊 GitHub API Consumption Report

Report Date: 2026-04-22 · Repository: github/gh-aw · Run: §24808188155

---

Today at a Glance

Metric	Value
🤖 Total Runs	39 (28 ✅ / 11 ❌)
🎯 Success Rate	71.8%
🔗 GitHub REST API Calls	10,594 (core quota consumed — includes reads, writes, and all GitHub API operations)
📝 Safe-Output Writes	21 (issues + PRs + comments + discussions created by safe-output tools)
⏱ Avg Duration	239s (p95: 450s)

---

🔗 GitHub API Calls Trend (90 days)

This is the first day of tracking, so there is no historical trend to compare against. Today's total of 10,594 REST API calls forms the baseline for future trend analysis. The rolling average will become meaningful once more data points are collected over the coming days.

---

🔗 GitHub API Calls by Workflow Trend (30 days)

With only one day of history, per-workflow trends are shown as a snapshot for today. Test Quality Sentinel (3,867 calls), Design Decision Gate (2,756 calls), and Smoke CI (2,421 calls) dominate consumption and will form the basis of trend lines as history accumulates over 30 days.

---

🔗 GitHub REST API Calls Heatmap (90 days)

As this is the first data point in the 90-day window, the chart shows a top-workflows bar chart as a fallback. Weekly calendar heatmap patterns will emerge as more data is collected. Today (2026-04-22) serves as the baseline entry for the heatmap history.

---

🍩 Top API Burners (24h)

Three workflows account for the majority of REST API consumption today: Test Quality Sentinel (36.5%), Design Decision Gate (26.0%), and Smoke CI (22.9%) together consume 85.4% of all core quota. The remaining 17 workflows share just 14.6%, indicating high concentration risk in these three automated testing and design-review workflows.

---

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

No workflow approaches the 15,000/hr core limit today — the highest consumer, Test Quality Sentinel, used only 3,867 calls across 8 runs (avg 483/run). However, at 8 runs per day it could become a concern at higher frequency. Optimising GitHub API calls in the Smoke CI family (9 runs, 269/run) could yield modest savings at scale.

---

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

Workflow	REST API Calls	Runs	Avg Duration
Test Quality Sentinel	3,867	8	321s
Design Decision Gate	2,756	8	239s
Smoke CI	2,421	9	203s
Daily Project Performance Summary Generator	836	1	418s
Daily Safe Output Integrator	114	1	295s
Smoke Copilot	106	1	450s
Smoke OpenCode	88	1	145s
Agent Container Smoke Test	78	1	203s
Smoke Codex	76	1	165s
Smoke Crush	72	1	120s

---

Trending Indicators

• 7-day API trend: → N/A (first data point — baseline established today)
• 30-day API trend: → N/A (first data point — baseline established today)
• GitHub REST API call rate: ~10,594 calls/day (1 data point; hourly limit: 15,000)

---

📦 Cache Memory Status

• Location: /tmp/gh-aw/cache-memory/trending/api-consumption/history.jsonl
• Data points stored: 1
• Earliest entry: 2026-04-22
• Retention policy: 90 days

---

Automatically generated by the api-consumption-report workflow.

Generated by GitHub API Consumption Report Agent · ● 367.8K · ◷

• expires on Apr 25, 2026, 11:44 PM UTC

[github-actions[bot]]

This discussion has been marked as outdated by GitHub API Consumption Report Agent.

A newer discussion is available at Discussion #28183.