gh-actions-samples
The purpose of this repo is to answer questions one might have about github actions, through examples. After you have seen the examples in this repo, you may want to also run them which is why anyone can test some of the actions by creating an issue that contains the action file's name (without the extension).
Each action will run when it detects an issue with it's name was created. It does this through the help of the issues event.
Ready❓ Go‼️
I want to...
Passing Parameters...
Caching...
📂 Caching on Linux...
Gathering Output
- Create an id for the step. Mind the syntax.
- Create the output(s) using the
set-outputcommand - Use the id and the output name in another step
outputs_from_step.yml
Creating environment variables
ℹ️ By using the env keyword on the entire workflow, a job or a step. Seeenv. Note: This variable CAN be used in the same place where it was createdℹ️ Through Github Actionsset-env. This will create an environment variable that can be used by all subsequent steps. Note: Variables created this way CANNOT be used in the same step where they were created, however following steps can see that variable
step_param_from_env.yml
Creating a cache on Linux
cache_deps_ubuntu.yml. (This one requires a push or pull_request event to be triggered and this is due mostly to a restriction of the cache action.)

Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.
