Repository navigation
Artifacts Usage Report #49719
Closed
Replies: 1 comment
|
This discussion was automatically closed because it expired on 2026-08-03T06:30:37.009Z.
|
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.
Analysis window: recent runs (last ~1 hour of activity captured in this run — GitHub's Artifacts API only exposes non-expired artifacts, and the most recent runs dominate the sample). 20 workflows had artifacts across 20 distinct runs, totaling 99 artifacts, ~~135 MB combined.
Methodology & data limitations
GET /repos/github/gh-aw/actions/artifacts(single page, most recent 99 non-expired artifacts returned by the API at query time — GitHub does not retain historical/expired artifact metadata beyond expiry, so this reflects a live snapshot rather than a true rolling 30-day history).run.workflow_run.id, then each run was resolved to its workflow name viaGET /repos/github/gh-aw/actions/runs/{id}.size_in_bytesconverted to MB/KB (1024-based).Insights & Recommendations
gh-awlock workflows use short retention windows, so long-term trend analysis isn't possible from a single snapshot.Recommendations:
retention-daysfurther or excluding these from artifact upload if not needed for debugging.agent,usage,aic-usage-cache) into a single combined archive per run to reduce artifact-count overhead.All reactions