Artifacts preserve workflow output
Actions artifacts can store files generated by a workflow, such as test reports, packaged applications or build archives. Artifacts are useful for passing outputs between jobs and inspecting results after a run.
Do not use artifacts as permanent secret storage
Artifacts should contain outputs appropriate for the repository's access model. Do not upload credentials, private keys or sensitive debugging dumps simply because an artifact is convenient.
Name artifacts clearly
A meaningful artifact name helps developers find the output associated with a specific workflow run.
ADVERTISEMENT