forked from nektos/act
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Added documentation for module not found issue.
- Loading branch information
Showing
1 changed file
with
57 additions
and
35 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,48 +1,50 @@ | ||
|  | ||
| # Overview [](https://github.com/nektos/act/actions) [](https://gitter.im/nektos/act?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge) [](https://goreportcard.com/report/github.com/nektos/act) | ||
|  | ||
|
|
||
| # Overview [](https://github.com/nektos/act/actions) [](https://gitter.im/nektos/act?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge) [](https://goreportcard.com/report/github.com/nektos/act) | ||
|
|
||
| > "Think globally, <code>act</code> locally" | ||
| Run your [GitHub Actions](https://developer.github.com/actions/) locally! Why would you want to do this? Two reasons: | ||
|
|
||
| * **Fast Feedback** - Rather than having to commit/push every time you want to test out the changes you are making to your `.github/workflows/` files (or for any changes to embedded GitHub actions), you can use `act` to run the actions locally. The [environment variables](https://help.github.com/en/actions/configuring-and-managing-workflows/using-environment-variables#default-environment-variables) and [filesystem](https://help.github.com/en/actions/reference/virtual-environments-for-github-hosted-runners#filesystems-on-github-hosted-runners) are all configured to match what GitHub provides. | ||
| * **Local Task Runner** - I love [make](https://en.wikipedia.org/wiki/Make_(software)). However, I also hate repeating myself. With `act`, you can use the GitHub Actions defined in your `.github/workflows/` to replace your `Makefile`! | ||
| - **Fast Feedback** - Rather than having to commit/push every time you want to test out the changes you are making to your `.github/workflows/` files (or for any changes to embedded GitHub actions), you can use `act` to run the actions locally. The [environment variables](https://help.github.com/en/actions/configuring-and-managing-workflows/using-environment-variables#default-environment-variables) and [filesystem](https://help.github.com/en/actions/reference/virtual-environments-for-github-hosted-runners#filesystems-on-github-hosted-runners) are all configured to match what GitHub provides. | ||
| - **Local Task Runner** - I love [make](<https://en.wikipedia.org/wiki/Make_(software)>). However, I also hate repeating myself. With `act`, you can use the GitHub Actions defined in your `.github/workflows/` to replace your `Makefile`! | ||
|
|
||
| # 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](https://help.github.com/en/actions/configuring-and-managing-workflows/using-environment-variables#default-environment-variables) and [filesystem](https://help.github.com/en/actions/reference/virtual-environments-for-github-hosted-runners#filesystems-on-github-hosted-runners) are all configured to match what GitHub provides. | ||
|
|
||
| Let's see it in action with a [sample repo](https://github.com/cplee/github-actions-demo)! | ||
|
|
||
|  | ||
|
|
||
| # Installation | ||
| To install with [Homebrew](https://brew.sh/), run: | ||
|
|
||
| ```brew install nektos/tap/act``` | ||
| To install with [Homebrew](https://brew.sh/), run: | ||
|
|
||
| `brew install nektos/tap/act` | ||
|
|
||
| Alternatively, you can use the following: | ||
| Alternatively, you can use the following: | ||
|
|
||
| ```curl https://raw.githubusercontent.com/nektos/act/master/install.sh | sudo bash``` | ||
| `curl https://raw.githubusercontent.com/nektos/act/master/install.sh | sudo bash` | ||
|
|
||
| If you are running Windows, download the [latest release](https://github.com/nektos/act/releases/latest) and add the binary into your PATH. | ||
| If you are using [Chocolatey](https://chocolatey.org/) then run: | ||
| ```choco install act-cli``` | ||
| `choco install act-cli` | ||
|
|
||
| If you are using [Scoop](https://scoop.sh/) then run: | ||
| ```scoop install act``` | ||
| `scoop install act` | ||
|
|
||
| If you are running Arch Linux, you can install the [act](https://aur.archlinux.org/packages/act/) package with your favorite package manager: | ||
|
|
||
| ```yay -S act``` | ||
| `yay -S act` | ||
|
|
||
| If you are using NixOS or the Nix package manager on another platform you can install act globally by running | ||
|
|
||
| ```nix-env -iA nixpkgs.act``` | ||
| `nix-env -iA nixpkgs.act` | ||
|
|
||
| or in a shell by running | ||
|
|
||
| ```nix-shell -p act``` | ||
| `nix-shell -p act` | ||
|
|
||
| # Commands | ||
|
|
||
|
|
@@ -67,6 +69,7 @@ act -v | |
| ``` | ||
|
|
||
| # Flags | ||
|
|
||
| ``` | ||
| -b, --bind bind working directory to container, rather than copy | ||
| -C, --directory string working directory (default ".") | ||
|
|
@@ -87,30 +90,46 @@ act -v | |
| -W, --workflows string path to workflow files (default "./.github/workflows/") | ||
| ``` | ||
|
|
||
| # Known Issues | ||
|
|
||
| MODULE_NOT_FOUND during `docker cp` command | ||
|
|
||
| ``` | ||
| steps: | ||
| - name: Checkout | ||
| uses: actions/checkout@v2 | ||
| with: | ||
| path: "your-action-root-directory" | ||
| ``` | ||
|
|
||
| # Runners | ||
| GitHub Actions offers managed [virtual environments](https://help.github.com/en/actions/reference/virtual-environments-for-github-hosted-runners) 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 | [node:12.6-buster-slim](https://hub.docker.com/_/buildpack-deps) | | ||
| | ubuntu-18.04 | [node:12.6-buster-slim](https://hub.docker.com/_/buildpack-deps) | | ||
| | ubuntu-16.04 | [node:12.6-stretch-slim](https://hub.docker.com/_/buildpack-deps) | | ||
| | windows-latest | `unsupported` | | ||
| | windows-2019 | `unsupported` | | ||
| | macos-latest | `unsupported` | | ||
| | macos-10.15 | `unsupported` | | ||
|
|
||
| GitHub Actions offers managed [virtual environments](https://help.github.com/en/actions/reference/virtual-environments-for-github-hosted-runners) 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 | [node:12.6-buster-slim](https://hub.docker.com/_/buildpack-deps) | | ||
| | ubuntu-18.04 | [node:12.6-buster-slim](https://hub.docker.com/_/buildpack-deps) | | ||
| | ubuntu-16.04 | [node:12.6-stretch-slim](https://hub.docker.com/_/buildpack-deps) | | ||
| | windows-latest | `unsupported` | | ||
| | windows-2019 | `unsupported` | | ||
| | macos-latest | `unsupported` | | ||
| | macos-10.15 | `unsupported` | | ||
|
|
||
| ## Default runners are intentionally incomplete | ||
|
|
||
| These default images do **not** contain **all** the tools that GitHub Actions offers by default in their runners. | ||
|
|
||
| ## Alternative runner images | ||
|
|
||
| If you need an environment that works just like the corresponding GitHub runner then consider using an image provided by [nektos/act-environments](https://github.com/nektos/act-environments): | ||
|
|
||
| * [nektos/act-environments-ubuntu:18.04](https://hub.docker.com/r/nektos/act-environments-ubuntu/tags) - built from the Packer file GitHub uses in [actions/virtual-environments](https://github.com/actions/runner). | ||
| - [nektos/act-environments-ubuntu:18.04](https://hub.docker.com/r/nektos/act-environments-ubuntu/tags) - built from the Packer file GitHub uses in [actions/virtual-environments](https://github.com/actions/runner). | ||
|
|
||
| :warning: :elephant: `*** WARNING - this image is >18GB 😱***` | ||
|
|
||
| ## Use an alternative runner image | ||
|
|
||
| To use a different image for the runner, use the `-P` option: | ||
|
|
||
| ``` | ||
|
|
@@ -121,27 +140,29 @@ act -P ubuntu-latest=nektos/act-environments-ubuntu:18.04 | |
|
|
||
| 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` - use `somevalue` as the value for `MY_SECRET`. | ||
| * `act -s MY_SECRET` - check for an environment variable named `MY_SECRET` and use it if it exists. If the environment variable is not defined, prompt the user for a value. | ||
| - `act -s MY_SECRET=somevalue` - use `somevalue` as the value for `MY_SECRET`. | ||
| - `act -s MY_SECRET` - check for an environment variable named `MY_SECRET` and use it if it exists. If the environment variable is not defined, prompt the user for a value. | ||
|
|
||
| # Configuration | ||
| You can provide default configuration flags to `act` by either creating a `./.actrc` or a `~/.actrc` file. Any flags in the files will be applied before any flags provided directly on the command line. For example, a file like below will always use the `nektos/act-environments-ubuntu:18.04` image for the `ubuntu-latest` runner: | ||
|
|
||
| You can provide default configuration flags to `act` by either creating a `./.actrc` or a `~/.actrc` file. Any flags in the files will be applied before any flags provided directly on the command line. For example, a file like below will always use the `nektos/act-environments-ubuntu:18.04` image for the `ubuntu-latest` runner: | ||
|
|
||
| ``` | ||
| # sample .actrc file | ||
| -P ubuntu-latest=nektos/act-environments-ubuntu:18.04 | ||
| ``` | ||
|
|
||
| Additionally, act supports loading environment variables from an `.env` file. The default is to look in the working directory for the file but can be overridden by: | ||
| Additionally, act supports loading environment variables from an `.env` file. The default is to look in the working directory for the file but can be overridden by: | ||
|
|
||
| ``` | ||
| act --env-file my.env | ||
| ``` | ||
|
|
||
| # Events | ||
| Every [GitHub event](https://developer.github.com/v3/activity/events/types) is accompanied by a payload. You can provide these events in JSON format with the `--eventpath` to simulate specific GitHub events kicking off an action. For example: | ||
|
|
||
| ``` pull-request.json | ||
| Every [GitHub event](https://developer.github.com/v3/activity/events/types) is accompanied by a payload. You can provide these events in JSON format with the `--eventpath` to simulate specific GitHub events kicking off an action. For example: | ||
|
|
||
| ```pull-request.json | ||
| { | ||
| "pull_request": { | ||
| "head": { | ||
|
|
@@ -153,6 +174,7 @@ Every [GitHub event](https://developer.github.com/v3/activity/events/types) is a | |
| } | ||
| } | ||
| ``` | ||
|
|
||
| ``` | ||
| act -e pull-request.json | ||
| ``` | ||
|
|
@@ -169,7 +191,7 @@ Want to contribute to act? Awesome! Check out the [contributing guidelines](CONT | |
|
|
||
| ## Building from source | ||
|
|
||
| * Install Go tools 1.11.4+ - (https://golang.org/doc/install) | ||
| * Clone this repo `git clone [email protected]:nektos/act.git` | ||
| * Run unit tests with `make check` | ||
| * Build and install: `make install` | ||
| - Install Go tools 1.11.4+ - (https://golang.org/doc/install) | ||
| - Clone this repo `git clone [email protected]:nektos/act.git` | ||
| - Run unit tests with `make check` | ||
| - Build and install: `make install` | ||