From 7044abc06f8add4a601d588d14d263b6dc623eea Mon Sep 17 00:00:00 2001 From: ChristopherHX Date: Sun, 1 Jun 2025 16:00:56 +0200 Subject: [PATCH 1/2] Clarify that this is a fork of nektos/act --- src/introduction.md | 31 ++++++++----------------------- 1 file changed, 8 insertions(+), 23 deletions(-) diff --git a/src/introduction.md b/src/introduction.md index 7ef1c65..6302b63 100644 --- a/src/introduction.md +++ b/src/introduction.md @@ -1,25 +1,10 @@ # Introduction -![act-logo](https://raw.githubusercontent.com/wiki/nektos/act/img/logo-150.png) - -> "Think globally, `act` 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](). However, I also hate repeating myself. With `act`, you can use the GitHub Actions defined in your `.github/workflows/` to replace your `Makefile`! - ---- - -> **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. - -Let's see it in action with a [sample repo](https://github.com/cplee/github-actions-demo)! - -![Demo](https://raw.githubusercontent.com/wiki/nektos/act/quickstart/act-quickstart-2.gif) +
+This is a derivative of [nektos/act](https://github.com/nektos/act) between version v0.2.71 from January 2025 and v0.2.72 February 2025 +
+ +- Support for macOS VMs using tart `-P tart://` +- `--use-new-action-cache` has been removed, the default clone mode of nektos/act has been removed +- CI tests are run in 6min compared to 17min on nektos/act +- Flags `--pull=false` and `--rebuild=false` are inverted to `--no-poll` and `--no-rebuild` From 794fd6c9e827fdd4a3a320cd301864be2883d4a5 Mon Sep 17 00:00:00 2001 From: ChristopherHX Date: Sun, 1 Jun 2025 14:11:51 +0000 Subject: [PATCH 2/2] fix style --- src/introduction.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/src/introduction.md b/src/introduction.md index 6302b63..16e4e2a 100644 --- a/src/introduction.md +++ b/src/introduction.md @@ -1,7 +1,10 @@ # Introduction
-This is a derivative of [nektos/act](https://github.com/nektos/act) between version v0.2.71 from January 2025 and v0.2.72 February 2025 + +This is a derivative of [nektos/act](https://github.com/nektos/act) +between version v0.2.71 from January 2025 and v0.2.72 February 2025 +
- Support for macOS VMs using tart `-P tart://`