From 85acf4bcdd3e4436990c5f3a086611565d6065b2 Mon Sep 17 00:00:00 2001 From: Sanjula Ganepola Date: Tue, 24 Dec 2024 11:32:13 -0500 Subject: [PATCH 1/4] Add GitHub Local Actions to README Signed-off-by: Sanjula Ganepola --- README.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/README.md b/README.md index a04c43b850d..2c4e0fc508e 100644 --- a/README.md +++ b/README.md @@ -9,6 +9,10 @@ Run your [GitHub Actions](https://developer.github.com/actions/) locally! Why wo - **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](). However, I also hate repeating myself. With `act`, you can use the GitHub Actions defined in your `.github/workflows/` to replace your `Makefile`! +> [!TIP] +> **Now Manage and Run Act Directly From VS Code!** +> Check out the [GitHub Local Actions](https://sanjulaganepola.github.io/github-local-actions-docs/) Visual Studio Code extension which allows you to leverage the power of `act` to run and test workflows locally without leaving your editor. + # 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://docs.github.com/en/actions/using-github-hosted-runners/about-github-hosted-runners#file-systems) are all configured to match what GitHub provides. From 4e3201f91dc053da382dcc2e951d3352c754cf3a Mon Sep 17 00:00:00 2001 From: Sanjula Ganepola Date: Sun, 19 Jan 2025 15:39:20 -0500 Subject: [PATCH 2/4] Remove trailing whitespace Signed-off-by: Sanjula Ganepola --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 2c4e0fc508e..db156af8dd1 100644 --- a/README.md +++ b/README.md @@ -10,7 +10,7 @@ Run your [GitHub Actions](https://developer.github.com/actions/) locally! Why wo - **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 your `Makefile`! > [!TIP] -> **Now Manage and Run Act Directly From VS Code!** +> **Now Manage and Run Act Directly From VS Code!** > Check out the [GitHub Local Actions](https://sanjulaganepola.github.io/github-local-actions-docs/) Visual Studio Code extension which allows you to leverage the power of `act` to run and test workflows locally without leaving your editor. # How Does It Work? @@ -38,4 +38,4 @@ Want to contribute to act? Awesome! Check out the [contributing guidelines](CONT - Install Go tools 1.20+ - () - Clone this repo `git clone git@github.com:nektos/act.git` - Run unit tests with `make test` -- Build and install: `make install` +- Build and install: `make install` \ No newline at end of file From 7da0e0cf7c3c4bb1731630665089aacc4b582f6d Mon Sep 17 00:00:00 2001 From: Sanjula Ganepola Date: Sun, 19 Jan 2025 15:47:50 -0500 Subject: [PATCH 3/4] Add line break after heading Signed-off-by: Sanjula Ganepola --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index db156af8dd1..83080dac0f9 100644 --- a/README.md +++ b/README.md @@ -10,7 +10,7 @@ Run your [GitHub Actions](https://developer.github.com/actions/) locally! Why wo - **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 your `Makefile`! > [!TIP] -> **Now Manage and Run Act Directly From VS Code!** +> **Now Manage and Run Act Directly From VS Code!**
> Check out the [GitHub Local Actions](https://sanjulaganepola.github.io/github-local-actions-docs/) Visual Studio Code extension which allows you to leverage the power of `act` to run and test workflows locally without leaving your editor. # How Does It Work? From 956a6b904e0928243246d391ab8687411e510452 Mon Sep 17 00:00:00 2001 From: Sanjula Ganepola Date: Sun, 19 Jan 2025 15:59:43 -0500 Subject: [PATCH 4/4] Restore final new line Signed-off-by: Sanjula Ganepola --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 83080dac0f9..26159e90a60 100644 --- a/README.md +++ b/README.md @@ -38,4 +38,4 @@ Want to contribute to act? Awesome! Check out the [contributing guidelines](CONT - Install Go tools 1.20+ - () - Clone this repo `git clone git@github.com:nektos/act.git` - Run unit tests with `make test` -- Build and install: `make install` \ No newline at end of file +- Build and install: `make install`