How do I make a workflow produce an artifact?

I’m trying to set up a build workflow for that produces several artifacts via a script. I’ve got as far as successfully running the build scripts via the workflow, which the logs indicate are producing the artifacts as expected, but I don’t see the artifact menu as described in https://help.github.com/en/articles/managing-a-workflow-run#downloading-logs-and-artifacts. Do I have to explicitly mark the files to be archived somehow?

3 Likes

I think to make artifacts show up there you can use GitHub’s upload-artifact action: https://github.community/t5/GitHub-Actions/Caching-files-between-GitHub-Action-executions/m-p/30172/highlight/true#M130

This is the actual upload-artifact action repo: https://github.com/actions/upload-artifact

2 Likes

More here:

https://help.github.com/en/articles/persisting-workflow-data-using-artifacts

1 Like

Is there a way to manually upload an artifact, without using GitHub’s upload-artifact action? Our organization has enabled the “Enable local actions only” restriction so we’re unable to use actions outside of our own repository.

1 Like

Isn’t the action open source? In which case, your organisation can simply fork to fix this issue?