Soft fork of https://github.com/nektos/act used by the Forgejo runner
Find a file
Carlos Alexandro Becker 9fd6310363
fix: clean code
2019-05-23 01:45:50 -03:00
.github resolve issues with release action 2019-02-07 09:50:30 -08:00
actions fix: added tests and improved code 2019-05-23 01:40:07 -03:00
cmd Add flag to skip pulling images already present 2019-02-18 21:12:35 -08:00
common fix: clean code 2019-05-23 01:45:50 -03:00
container Ignore error, vet failure 2019-03-09 18:38:35 -08:00
vendor --watch 2019-02-09 20:39:09 -06: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 add support for 'reuse' mode to allow act to be used for a fast local task runner 2019-01-17 14:53:35 -08:00
.goreleaser.yml fail on error (#20) 2019-01-23 11:51:22 -08:00
CONTRIBUTING.md Initial commit with support for GitHub actions 2019-01-12 20:45:25 -08:00
go.mod --watch 2019-02-09 20:39:09 -06:00
go.sum --watch 2019-02-09 20:39:09 -06:00
install.sh 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
main.go Initial commit with support for GitHub actions 2019-01-12 20:45:25 -08:00
Makefile Capture errors from docker log output 2019-03-01 21:16:43 -06:00
README.md s/pull-request/pull_request 2019-04-02 11:11:59 -07:00

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

"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 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 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!

Demo

Installation

To install with Homebrew, run:

brew tap nektos/tap && 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 -a test

# Run in dry-run mode:
act -n

# Run in reuse mode to save state:
act -r

# Enable verbose-logging (can be used with any of the above commands)
act -v

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