ad2789fa1b
Signed-off-by: Casey Lee <cplee@nektos.com> |
||
---|---|---|
.github | ||
cmd | ||
pkg | ||
vendor | ||
.editorconfig | ||
.gitignore | ||
.golangci.yml | ||
.goreleaser.yml | ||
CONTRIBUTING.md | ||
go.mod | ||
go.sum | ||
install.sh | ||
LICENSE | ||
main.go | ||
Makefile | ||
README.md |
Overview
"Think globally,
act
locally"
Run your GitHub Actions locally! Why would you want to do this? Two reasons:
- Fast Feedback - Rather than having to commit/push every time you want test out the changes you are making to your
.github/workflows/
files (or for any changes to embedded GitHub actions), you can useact
to run the actions locally. The environment variables and filesystem are all configured to match what GitHub provides. - Local Task Runner - I love make. However, I also hate repeating myself. With
act
, you can use the GitHub Actions defined in your.github/workflows/
to replace yourMakefile
!
How Does It Work?
When you run act
it reads in your GitHub Actions from .github/workflows/
and determines the set of actions that need to be run. It uses the Docker API to either pull or build the necessary images, as defined in your workflow files and finally determines the execution path based on the dependencies that were defined. Once it has the execution path, it then uses the Docker API to run containers for each action based on the images prepared earlier. The environment variables and filesystem are all configured to match what GitHub provides.
Let's see it in action with a sample repo!
Installation
To install with Homebrew, run:
brew install nektos/tap/act
Alternatively, you can use the following:
curl https://raw.githubusercontent.com/nektos/act/master/install.sh | sudo bash
If you are running Arch Linux, you can install the act package with your favorite package manager:
yay -S act
Commands
# List the actions
act -l
# Run the default (`push`) event:
act
# Run a specific event:
act pull_request
# Run a specific job:
act -j test
# Run in dry-run mode:
act -n
# Enable verbose-logging (can be used with any of the above commands)
act -v
Platforms
GitHub Actions offers managed virtual environments for running workflows. In order for act
to run your workflows locally, it must run a container for the runner defined in your workflow file. Here are the images that act
uses for each runner type:
GitHub Runner | Docker Image |
---|---|
ubuntu-latest | ubuntu:18.04 |
ubuntu-18.04 | ubuntu:18.04 |
ubuntu-16.04 | ubuntu:16.04 |
windows-latest | unsupported |
windows-2019 | unsupported |
macos-latest | unsupported |
macos-10.15 | unsupported |
These default images do not contain all the tools that GitHub Actions offers by default in their runners. If you need an environment that works just like the corresponding GitHub runner then consider using an image provided by nektos/act-environments:
- nektos/act-environments-ubuntu:18.04 - built from the Packer file GitHub uses in actions/virtual-environments.
*** WARNING - this image is >18GB 😱***
To use a different image for the runner, use the -P
option:
act -P ubuntu-latest=nektos/act-environments-ubuntu:18.04
Secrets
To run act
with secrets, you can enter them interactively or supply them as environment variables. The following options are available for providing secrets:
act -s MY_SECRET=somevalue
- usesomevalue
as the value forMY_SECRET
.act -s MY_SECRET
- check for an environment variable namedMY_SECRET
and use it if it exists. If environment variable is not defined, prompt the user for a value.
Support
Need help? Ask on Gitter!
Contributing
Want to contribute to act? Awesome! Check out the contributing guidelines to get involved.
Building from source
- Install Go tools 1.11.4+ - (https://golang.org/doc/install)
- Clone this repo
git clone git@github.com:nektos/act.git
- Run unit tests with
make check
- Build and install:
make install