[api-consumption] 📊 GitHub API Consumption Report — 2026-10-18

[github-actions[bot]]

📊 GitHub API Consumption Report

Report Date: 2026-10-18 · Repository: github/gh-aw · Run: #39120393655

---

Today at a Glance

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

---

🔗 GitHub API Calls Trend (90 days)

The daily API consumption trend is currently sparse because cache history was being backfilled. The visible period shows low absolute usage with no sustained upward acceleration yet. As more daily entries accumulate, this chart will stabilise into a clearer long-term directional signal.

---

🔗 GitHub API Calls by Workflow Trend (30 days)

Workflow-level trend lines show a low-throughput baseline across the collected dataset. No single workflow displays a persistent multi-week surge in API demand. Current distribution suggests episodic usage spikes rather than steady high-burn behavior.

---

🔗 GitHub REST API Calls Heatmap (90 days)

The heatmap indicates scattered activity with several low-intensity days and limited clustering. Weekly cadence appears irregular during this partial backfill window. No recurring weekday hotspot stands out strongly at present.

---

🍩 Top API Burners (24h)

API consumption concentration is modest in this sample, with top workflows accounting for most observed calls on active days. Because overall volume is low, share percentages can shift quickly from run to run. Continue monitoring for concentration risk if a single workflow’s share grows materially.

---

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

The top REST API consumers are well below the 15,000/hour GitHub core limit. No workflow in the collected dataset is close to quota stress. Optimisation opportunities are mainly preventative: reduce redundant list/read calls and keep pagination bounded.

---

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

Workflow	REST API Calls	Runs	Avg Duration
CI	0	8	34.8s
Dependency review	0	7	16.8s
Feature Request	0	7	16.1s
Landing page issue	0	4	17.6s
Add skipped-date support to maintenance mode script	0	3	16.4s
Documentation issue	0	3	16.4s
New Workflow Request	0	3	16.6s
stale	0	3	16.4s
Add Release Note issue	0	2	16.8s
Agentic Workflow Bug report	0	2	16.2s

---

Trending Indicators

• 7-day API trend: → (insufficient data) vs. previous 7 days
• 30-day API trend: → (insufficient data) vs. prior 30 days
• GitHub REST API call rate: 0.0 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: no (first run)
• Collection mode: backfill
• Logs start_date used: -90d
• Data points stored: 18
• Earliest entry: 2026-10-01
• Retention policy: 90 days

---

Notes

• Log collection used existing downloaded run directories after bounded retries on agenticworkflows logs timed out, so this dataset may be partial.

---

Automatically generated by the api-consumption-report workflow.

Generated by 📊 GitHub API Consumption Report Agent · codex · auto · 30.2 AIC · ⌖ 20.2 AIC · ⊞ 23.6K · ◷

• expires on Oct 21, 2026, 2:54 AM UTC-08:00

[github-actions[bot]]

This discussion was automatically closed because it expired on 2026-10-21T10:54:44.657Z.

Closed by Workflow