[api-consumption] π GitHub API Consumption Report β 2026-07-11 #44940
Closed
Replies: 1 comment
-
|
This discussion has been marked as outdated by GitHub API Consumption Report Agent. A newer discussion is available at Discussion #45077. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
π GitHub API Consumption Report
Report Date: 2026-07-11 Β· Repository: github/gh-aw Β· Run: #29150297447
Today at a Glance
π GitHub API Calls Trend (90 days)
The 7-day rolling average has climbed sharply as PR-review and skills-reviewer workflows ramped up, but the daily series is highly volatile β days range from ~1.1k calls (06-30, only 12 runs) to a 574k spike (06-17). Today's 96.9k sits above the 90-day mean (~61.6k) yet well below the 07-04/07-05/07-08 peaks. Much of the swing reflects varying partial-collection window sizes and daily run-count changes rather than a pure per-run efficiency shift.
π GitHub API Calls by Workflow Trend (30 days)
The PR-quality cluster β Impeccable Skills Reviewer, Matt Pocock Skills Reviewer, PR Code Quality Reviewer, and Design Decision Gate β consistently tops per-workflow consumption, alongside Smoke CI. These review agents each run many times per day (13β14 runs today) and dominate the trend lines; no single new workflow has emerged as an outlier consumer in the last 30 days.
π GitHub REST API Calls Heatmap (90 days)
The heatmap shows consumption concentrated on weekdays, tracking PR activity, with lighter weekend cells. The hottest cells align with early-July high-run days (07-04, 07-05, 07-08). The 2026-07-09 gap (only sparse late-night runs, no entry recorded) appears as an empty cell and remains a known hole in the series.
π© Top API Burners (24h)
The top 3 workflows β Smoke CI (11.8k), Impeccable Skills Reviewer (10.2k), and Matt Pocock Skills Reviewer (10.2k) β together consume 33.3% of today's 96.9k core quota. Consumption is fairly distributed across the top 8 review/CI workflows rather than concentrated in one, which lowers single-workflow throttling risk.
π GitHub REST API Consumption by Workflow (last 24h)
The heaviest consumers are the PR-review agents and Smoke CI, each in the 7kβ12k range across 10β14 runs (~800β1.2k per run). No individual run approached the 15,000/hr core limit, so there is headroom. Optimisation opportunities: cache repeated
git/ghreads within the skills-reviewer agents and consolidate redundant PR metadata fetches in the review cluster.Top 10 Workflows by REST API Consumption (last 24h)
Trending Indicators
π¦ Cache Memory Status
/tmp/gh-aw/cache-memory/trending/api-consumption/history.jsonlπ Safe-Output Writes Breakdown (24h)
Total: 288 writes across 21 types.
add_comment: 68create_pull_request_review_comment: 51submit_pull_request_review: 46create_issue: 41add_labels: 15assign_to_agent: 15create_discussion: 13create_pull_request: 9update_pull_request: 8push_to_pull_request_branch: 4update_issue: 4comment_memory: 3create_check_run: 2send_slack_message: 2post_slack_message: 1create_code_scanning_alert: 1add_reviewer: 1upload_artifact: 1set_issue_type: 1remove_labels: 1update_release: 1Automatically generated by the api-consumption-report workflow.
Warning
Firewall blocked 1 domain
The following domain was blocked by the firewall during workflow execution:
awmgmcpgSee Network Configuration for more information.
Beta Was this translation helpful? Give feedback.
All reactions