Artifacts Usage Report — github/gh-aw (March 2026) #22238
Closed
Replies: 1 comment
-
|
This discussion was automatically closed because it expired on 2026-03-23T05:59:51.179Z.
|
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.
-
This report summarizes GitHub Actions artifact usage across the
github/gh-awrepository, based on analysis of 14 key workflows (out of 234 total) sampled from recent runs as of 2026-03-22.Overview
The repository runs 234 workflows with a combined volume of well over 100,000 runs per month. Artifact generation is concentrated in a handful of workflows — most of the high-frequency workflows (Scout, Mergefest, Plan Command) generate no artifacts at all. The workflows that do generate artifacts fall into two tiers: large infrastructure workflows (CI, Doc Build) and recurring agentic workflows with cache/memory patterns.
Artifact Summary by Workflow
github-pagesartifact; 1-day retentionEstimated Total Storage (Active Artifacts)
Insights
Top Storage Consumers
Doc Build - Deploy generates
github-pagesartifacts at ~223 MB each. With 10+ main-branch pushes per day and 1-day retention, this alone contributes ~2 GB of active storage at any given moment. Each artifact contains the full compiled static documentation site.CI creates 37 artifacts per run — the largest contributor by artifact count. The binary artifact (
gh-aw-linux-amd64, ~9 MB) and test/coverage reports (coverage-report,test-result-unit) dominate per-run size. With ~10 CI runs per day and 14-day retention for most artifacts, total CI storage is estimated at ~1.8 GB.Smoke Codex generates larger artifacts than Claude/Copilot equivalents. The
agentartifact reaches 1.4 MB andqmd-indexadds another 1 MB — roughly 5× larger than Smoke Claude per run. Over 2,387 runs at 90-day retention, this contributes meaningfully to total storage.Artifact Types and Patterns
Common artifact types identified across agentic workflows:
github-pagesgh-aw-linux-amd64coverage-reporttest-result-unitcache-memoryagentsafe-outputs-assetsrepo-memory-defaultdetectionactivationsafe-output-itemsapmPattern observed: Agentic workflows produce two tiers of artifacts:
activation,safe-outputs-assets,repo-memory-default,apm— ephemeral data only needed within the workflow runcache-memory,agent,detection,safe-output-items— persistent state and outputsHigh-Volume Workflows Without Artifacts
Several of the highest-volume workflows generate zero artifacts:
These workflows collectively account for ~49% of all workflow runs but contribute nothing to artifact storage — a positive efficiency indicator. Scout and Plan Command have the highest run volumes in the repository.
Recommendations
Review Doc Build retention policy —
github-pagesartifacts are automatically set to 1-day retention, which is appropriate. However, at ~223 MB per artifact and 10+ runs/day on main, consider whether all branch CI pushes trigger documentation builds or only main.Consolidate CI test result artifacts — The CI workflow currently generates ~26 separate integration test result artifacts. These could be consolidated into a single
test-resultsartifact using artifact merge, reducing artifact count from 37 to ~12 per run without losing data.Audit cache-memory retention — Several agentic workflows store
cache-memoryartifacts for 90 days. Verify that workflows reading these artifacts can handle stale/missing data gracefully, and consider reducing to 30 days for workflows that run daily (the memory would be refreshed 90× within the retention window anyway).Monitor Smoke Codex growth —
qmd-indexartifacts were not present in Claude/Copilot smoke runs, suggesting this is a newer feature. At ~1 MB per run × 90-day retention × daily runs = ~90 MB and growing, this warrants monitoring.Add a 30-day rolling analysis — Run this artifact analysis workflow weekly to track storage trends and catch regressions before they accumulate.
References:
Beta Was this translation helpful? Give feedback.
All reactions