Go to file
Casey Lee 6f07c10d8c
improve linting
2019-01-15 17:41:02 -08:00
.github Initial commit with support for GitHub actions 2019-01-12 20:45:25 -08:00
actions improve linting 2019-01-15 17:41:02 -08:00
cmd Initial commit with support for GitHub actions 2019-01-12 20:45:25 -08:00
common improve linting 2019-01-15 17:41:02 -08:00
container improve linting 2019-01-15 17:41:02 -08:00
example Initial commit with support for GitHub actions 2019-01-12 20:45:25 -08:00
.editorconfig Initial commit with support for GitHub actions 2019-01-12 20:45:25 -08:00
.gitignore Initial commit with support for GitHub actions 2019-01-12 20:45:25 -08:00
.golangci.yml improve linting 2019-01-15 17:41:02 -08:00
.goreleaser.yml Initial commit with support for GitHub actions 2019-01-12 20:45:25 -08:00
CONTRIBUTING.md Initial commit with support for GitHub actions 2019-01-12 20:45:25 -08:00
LICENSE Initial commit 2019-01-02 11:53:43 -08:00
Makefile improve linting 2019-01-15 17:41:02 -08:00
README.md readme update 2019-01-15 08:26:10 -08:00
go.mod Initial commit with support for GitHub actions 2019-01-12 20:45:25 -08:00
go.sum Initial commit with support for GitHub actions 2019-01-12 20:45:25 -08:00
install.sh Initial commit with support for GitHub actions 2019-01-12 20:45:25 -08:00
main.go Initial commit with support for GitHub actions 2019-01-12 20:45:25 -08:00

README.md

Join the chat at https://gitter.im/nektos/act Go Report Card

Overview

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 main.workflow file (or for any changes to embedded GitHub actions), you can use act 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 main.workflow file to replace your Makefile!

How Does It Work?

When you run act it reads in your GitHub Actions from .github/main.workflow 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 main.workflow file and finally determines the execution path based on the dependencies that were defined. Once it has the execution path, it the 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!

Demo

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

Commands

# List the actions
act -l

# Run the default (`push`) event:
act

# Run a specific event:
act pull-request

# Run a specific action:
act -t test

# Run in dry-run mode:
act -n

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+ - (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