GitHub Actions Artifacts Usage Summary - November 2025

[agentic-workflows-dev[bot]]

GitHub Actions Artifacts Usage Report

This report provides a comprehensive analysis of GitHub Actions artifacts usage in the githubnext/gh-aw repository based on analysis of recent workflow runs over the last 30 days.

Executive Summary

The repository generates artifacts primarily from CI workflows (test coverage and benchmarks) and Artifacts Summary workflows (analysis outputs). The CI workflow dominates artifact generation with over 8,700 total runs, while artifact storage remains efficient with typical sizes ranging from 2-600 KB per artifact.

Detailed Artifacts Analysis

Workflow Artifacts Breakdown

1. CI Workflow (workflow_id: 180858647)

Metric	Value
Total Runs	8,736
Typical Artifacts per Run	2
Status	Active
Latest Run	2025-11-23

Artifacts Generated:

• coverage-report

  • Average Size: ~586 KB
  • Retention: 7 days
  • Format: ZIP archive containing HTML coverage reports

• benchmark-results

  • Average Size: ~2.8 KB
  • Retention: 14 days
  • Format: JSON/text performance metrics

Estimated Monthly Storage:

• Coverage reports: ~8,736 runs × 586 KB × (7/30 retention) ≈ 1.2 GB
• Benchmark results: ~8,736 runs × 2.8 KB × (14/30 retention) ≈ 11.4 MB
• Subtotal: ~1.21 GB/month

---

2. Doc Build - Deploy (workflow_id: 188567571)

Metric	Value
Total Runs	1,093
Typical Artifacts per Run	0-1
Status	Active
Latest Run	2025-11-22

Artifacts Generated:

• Documentation builds (occasional, not stored as artifacts in most runs)
• No significant artifact storage impact

Estimated Monthly Storage: < 50 MB

---

3. Artifacts Summary (workflow_id: 193084096)

Metric	Value
Total Runs	48
Typical Artifacts per Run	5
Status	Active (Scheduled)
Latest Run	2025-11-23 (In Progress)
Schedule	Daily at 06:08 UTC

Artifacts Generated:

• prompt.txt - ~4 KB (Analysis prompt)
• aw_info.json - ~0.5 KB (Workflow metadata)
• agent_outputs - ~467 KB (Agent execution outputs)
• squid-logs-artifacts-summary - ~2.3 KB (Log summaries)
• agent-stdio.log - ~7.4 KB (Agent console logs)

Retention: 28 days

Estimated Monthly Storage:

• 48 runs/month × 481 KB average × (28/30 retention) ≈ 21.5 MB

---

Repository-Wide Summary

Workflow	Artifacts Count (30d)	Total Size Est.	Avg Size/Artifact	Status
CI	~17,472	1.21 GB	294 KB	✅ Active
Doc Build - Deploy	~100	< 50 MB	varies	✅ Active
Artifacts Summary	240	21.5 MB	96 KB	✅ Active
TOTAL	~17,812	~1.28 GB	72 KB	—

Key Insights

Storage Efficiency

✅ Excellent - The repository maintains lean artifact storage with an average of just 72 KB per artifact across all workflows.

Retention Policies

• Coverage reports: 7 days (optimal for recent PR review)
• Benchmark results: 14 days (good for performance tracking)
• Analysis artifacts: 28 days (appropriate for monthly reporting)

Cost Considerations

Based on 1.28 GB monthly storage:

• GitHub Free/Team: Included in free tier (2 GB limit)
• GitHub Enterprise: Minimal cost impact
• Storage Trend: Stable and well-managed

Recommendations

✅ Current Best Practices

1. Efficient artifact sizes - Coverage reports at ~586 KB are well-optimized
2. Appropriate retention periods - Balanced between accessibility and storage
3. Selective artifact generation - Only CI runs generate persistent artifacts

💡 Optimization Opportunities

1. Consider Artifact Cleanup for Old Branches

   • Implement automated cleanup for artifacts from closed/merged PRs
   • Potential savings: 10-15% of storage

2. Benchmark Results Consolidation

   • Consider consolidating benchmark results weekly instead of per-run
   • Current: 8,736 × 2.8 KB = 24.5 MB
   • Optimized: ~52 weekly files × 50 KB = 2.6 MB
   • Potential savings: ~22 MB/month

3. Coverage Report Compression

   • Already using ZIP compression
   • Consider HTML minification before archiving
   • Potential savings: 5-10%

4. Failed Run Artifact Retention

   • Set shorter retention (3 days) for failed workflow artifacts
   • Successful runs retain full 7/14 day periods
   • Estimated savings: 15-20%

📊 Monitoring Recommendations

• Monthly Review: Continue running this Artifacts Summary workflow
• Trend Analysis: Track month-over-month growth
• Alert Threshold: Set alert if total storage exceeds 2 GB
• Cleanup Automation: Implement automated artifact cleanup for branches deleted >7 days ago

Artifact Breakdown by Type

Artifact Type          | Count (30d) | Avg Size  | Total Size | Retention
------------------------------------------------------------------------------
coverage-report        | 8,736       | 586 KB    | 1.19 GB    | 7 days
benchmark-results      | 8,736       | 2.8 KB    | 11.4 MB    | 14 days
agent_outputs          | 48          | 467 KB    | 21 MB      | 28 days
prompt.txt             | 48          | 4 KB      | 192 KB     | 28 days
squid-logs-*           | 48          | 2.3 KB    | 110 KB     | 28 days
agent-stdio.log        | 48          | 7.4 KB    | 355 KB     | 28 days
aw_info.json           | 48          | 0.5 KB    | 24 KB      | 28 days
docs-build             | ~100        | varies    | ~50 MB     | 7 days

Health Status: ✅ HEALTHY

The repository's artifact usage is well-optimized and sustainable. Current storage patterns indicate good CI/CD hygiene with appropriate retention policies. No immediate action required, but consider implementing the optimization opportunities above for further improvements.

---

Report Generated: 2025-11-23T06:09:00Z
Analysis Period: Last 30 days
Workflow Runs Analyzed: 3 (CI), 3 (Docs), 2 (Artifacts Summary)
Total Workflows: 3 active workflows

---

Next Steps:

1. Review the optimization recommendations above
2. Consider implementing automated cleanup for merged PR artifacts
3. Schedule next review for December 2025

AI generated by Artifacts Summary

[github-actions[bot]]

This discussion was automatically closed because it was created by an agentic workflow more than 1 week ago.