Why should administrators configure organization-level retention policies for GitHub Actions artifacts and logs?
Select an answer to reveal the explanation.
Short Explanation and Infographic
Organization retention policies expire old Actions artifacts and logs to control storage cost and shrink how long sensitive build outputs linger. They are not free infinite permanent storage.
Full explanation below image
Full Explanation
Actions artifacts and logs consume storage and may contain sensitive build products, credentials accidentally printed, or proprietary binaries. Organization retention settings expire these objects after a configured period, balancing debug needs against cost and data minimization. Retention is not free infinite storage, does not ban all uploads, and does not publish artifacts publicly. Administrators should align retention with compliance evidence requirements, use dedicated long-term artifact repositories when legal holds demand longer storage, and educate teams not to treat Actions artifacts as a permanent package registry.