What can repository or organization administrators configure regarding Actions artifacts?
Select an answer to reveal the explanation.
Short Explanation
Artifacts pile up and cost storage. Set retention so yesterday's 2GB build logs don't live forever unless compliance says so. You still get artifacts when you upload them; admins just control how long they stick around and who can access them under normal repo permissions.
Full Explanation
The correct choice is configuring retention periods so artifacts expire and free storage after a defined time. This controls storage growth and reduces lingering sensitive build outputs. The idea that artifacts never exist even when upload-artifact runs successfully is false. Mandatory public exposure of all artifacts without authentication is insecure and incorrect as a default goal. Replacing Git history with artifact blobs only is also false. Align retention with compliance needs, purge sensitive artifacts sooner, and prefer attestations/packages for release artifacts that must persist.