From 54b93d7547414226be59eb31f1bb6a6621959721 Mon Sep 17 00:00:00 2001 From: Casey Lee Date: Fri, 18 Jan 2019 08:28:09 -0800 Subject: [PATCH] readme update --- README.md | 12 +++++++++++- 1 file changed, 11 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index b9e3f2e..0e2b951 100644 --- a/README.md +++ b/README.md @@ -1,8 +1,18 @@ - + + + + + +
+ + +

"Think globally, act locally"

[![Join the chat at https://gitter.im/nektos/act](https://badges.gitter.im/nektos/act.svg)](https://gitter.im/nektos/act?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge) [![Go Report Card](https://goreportcard.com/badge/github.com/nektos/act)](https://goreportcard.com/report/github.com/nektos/act) +
# Overview + 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 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](https://developer.github.com/actions/creating-github-actions/accessing-the-runtime-environment/#environment-variables) and [filesystem](https://developer.github.com/actions/creating-github-actions/accessing-the-runtime-environment/#filesystem) are all configured to match what GitHub provides.