📦 GitHub Actions Artifacts Usage Report (Last 30 Days) #31312
Closed
Replies: 1 comment
-
|
This discussion was automatically closed because it expired on 2026-05-11T06:33:38.809Z.
|
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
Analysis of 583 artifacts across 51 workflows with a combined size of 1.71 GB, collected from 391 non-cancelled runs between April 10 – May 10, 2026.
Key Findings
Doc Build - Deploy— 1.18 GB across only 5 runs (~242 MB each)CI— 261 artifacts at 91.2 MB total (avg 358 KB each, very efficient)CGO— 56 artifacts at 80.4 MB (avg 1.4 MB)Daily Skill Optimizer Improvementsgenerates large artifacts (~16 MB each)Summary Table
Insights & Recommendations
📊 Storage Distribution
💡 Optimization Recommendations
1. Doc Build - Deploy (1.18 GB, 69% of total storage)
The documentation build artifacts are by far the biggest consumers. Consider:
tar.gz)2. Many daily agentic workflows (~5 MB each)
About 40 daily workflows each produce ~5 MB artifacts. These likely contain agent session logs/outputs. Consider:
3. CGO artifacts (56 artifacts, 80 MB)
Cross-compilation artifacts are numerous. If these are binary releases, keep them; if they're intermediate build outputs, reduce retention.
4. Daily Skill Optimizer Improvements (16 MB avg)
Largest average size among agentic workflows. Review what's being uploaded — could contain unnecessary files.
Totals
References: §25621800830
Beta Was this translation helpful? Give feedback.
All reactions