Artifacts Usage Report — github/gh-aw #28558
Closed
Replies: 1 comment
-
|
This discussion was automatically closed because it expired on 2026-04-27T06:24:49.503Z.
|
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.
-
Overview
This report summarizes GitHub Actions artifact usage across the
github/gh-awrepository. The repository has 267 registered workflows and over 481,000 total workflow runs. Analysis focused on active workflows with recent runs and measured per-run artifact profiles.Key finding: Artifact generation is concentrated in the Smoke test suite (Claude, Codex, Copilot, OpenCode) which runs on every pull request. The
agentartifact (workflow session logs/context) anddetectionartifact (threat/content analysis) are the primary persistent storage consumers. Most workflows produce short-livedactivationartifacts (1-day TTL) that do not accumulate.Artifact Summary Table
Artifact Type Breakdown
Standard artifact types produced by agentic (lock.yml) workflows
activationagentdetectionsafe-outputs-itemsrepo-memory-defaultgh-aw(binary)safe-outputs-upload-artifactsdockerbuildcode-scanning-sarifapmsecret-validation-reportTop Storage Consumers
Workflows generating the most persistent artifact storage (90-day window):
🔴 Smoke Codex — 1.65 MB/run × ~370 runs/month ≈ 610 MB/month persistent
agentartifacts (~1.5 MB each, containing full Codex session logs)detectionartifacts unusually large (~185 KB vs. ~3 KB for other smoke tests)🟠 Smoke Copilot — 0.49 MB/run × ~388 runs/month ≈ 190 MB/month persistent
gh-aw, ~26.6 MB) and safe-output upload (~10 MB) expire in 1 day, limiting accumulation🟡 Smoke Claude — 0.43 MB/run × ~372 runs/month ≈ 160 MB/month persistent
detectionartifacts notably larger (~27 KB) vs. other smoke tests (~3 KB)🟢 Contribution Check — 0.54 MB/run (per-PR frequency) — variable total
🟢 Daily News — ~81 KB/run × ~24 runs/month ≈ 1.9 MB/month persistent
Insights & Recommendations
💡 Optimization Opportunities
Smoke Codex
agentartifacts are 3–4× larger than other smoke tests (~1.5 MB vs. ~400–500 KB). Investigate whether Codex session output can be truncated or compressed before upload. This workflow accounts for the single largest persistent storage category.Smoke Copilot uploads
gh-awbinary (~26.6 MB) andsafe-outputs-upload(~10 MB) per run — these expire after 1 day which is appropriate. No action needed, but worth monitoring if TTL policies change.repo-memory-defaultartifacts in Daily News (~1.28 MB) expire in 1 day — this is correct behavior for cross-run cache-memory. Functioning as designed.Activation artifacts (1-day TTL) are created by every agentic workflow — these are intentionally short-lived and not a storage concern.
High-volume workflows (CI: 24K runs, Scout: 34K runs, Doc Build: 8K runs) generate zero artifacts — excellent. These are well-optimized.
267 total workflows, majority generate no artifacts — the repo follows a healthy "artifacts only when needed" pattern.
📊 Estimated 90-Day Artifact Accumulation
Based on run frequency and 90-day retention:
Recommendations
Investigate Smoke Codex agent artifact size — at 1.5 MB/run, this is the top storage concern. Consider compressing logs or filtering verbose output before artifact upload.
Review
detectionartifact size for Smoke Codex — at 185 KB vs. 3–27 KB for other smoke tests, this may indicate a configuration or output verbosity difference.Monitor total storage usage via GitHub's billing/storage UI to validate these estimates against actual usage.
No action needed for workflows without artifacts (CI, Scout, Doc Build, etc.) — these are correctly configured.
References:
Beta Was this translation helpful? Give feedback.
All reactions