运行依赖 Docker,需先装好并启动 Docker;从源码构建需 Go 1.26.0(以 go.mod 为准);make test 需要 Docker,无 Docker 只能用 make test-fast
git clone [email protected]:nektos/act.git
make installREADME 未说明具体硬件要求,但运行依赖 Docker,需本机可用 Docker API
在本地跑 GitHub Actions 工作流,省去反复提交推送验证 CI 的时间
在本地直接跑 GitHub Actions 工作流,不用每次改完都推到远端等 CI,调试 workflow 和排查失败步骤快很多。
核心能力
- 读取 .github/workflows 并解析依赖执行顺序
- 通过 Docker API 拉取或构建镜像并逐 action 起容器
- 环境变量与文件系统对齐 GitHub 托管 runner
- 可当作本地任务运行器替代 Makefile
容易踩的坑
- v0.2.97最新正式版2026-11-04 · 2026-11-04 16:35 UTC
Changelog
Bug fixes
- 2540ba6c49dfbafe167d655e4044921cd2ed19e7 fix: mask nested secrets longest-first (GHSA-5xfg)
- v0.2.962026-11-03 · 2026-11-03 16:17 UTC
查看更新说明
Changelog
Bug fixes
- 52d11769b6f63de314821524bf116492d18ed1d7 fix(runner): contain reusable workflow paths and local repository build contexts (GHSA-9j7q-g3ch-2283)
- v0.2.952026-11-03 · 2026-11-03 03:52 UTC
查看更新说明
Changelog
Bug fixes
- a456b6b560db74fc0c59fcde385c0d29ff4f4517 fix(actrc): one flag per project .actrc line (GHSA-jpm2-x6wf-fxjc)
- v0.2.942026-10-31 · 2026-10-31 19:36 UTC
查看更新说明
Changelog
Bug fixes
- 3fde8e609623104b099747ff67166561ecb7e6be fix(runner): check docker context against the executor workspace
Other
- ec4776c6fe62d8225f5eaad0a7563e8f271f1de5 chore(runner): fix lint in action path containment
- v0.2.932026-10-31 · 2026-10-31 18:34 UTC
查看更新说明
Changelog
Bug fixes
- 66cee43c1e979eecdb617c061bb22a5b74d2bd76 fix(runner): keep local action paths and docker build contexts inside the workspace
- cf5130ce8d9417fa9ac5578e44a79ef8a3b6ba26 fix(git): keep brackets on IPv6 enterprise SSH hosts
- cb08f1430856a61608f47c436fbb6dc74aac26ff fix(git): keep userinfo out of query/fragment and drop HTTPS port for GHE SSH
- 3311ed9e8f5dfab18e1168aa2704a0a1d8e74ee4 fix(git): match GitHub remotes with ports and git:// URLs again
Other
- 2b8b3d68ed685175a6b68526d781a557a436e0ef chore(testdata): drop vulnerable npm deps from fixture actions
- c365046443003bbc14b18ac2ace8a4f6fd23383e test(git): silence secretlint on fake credential fixture
用户点评
登录用户的真实使用记录,可按版本和硬件筛选还没有人点评。第一个说出真实体验的人最有价值。
Overview

"Think globally,
actlocally"
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 to test out the changes you are making to your
.github/workflows/files (or for any changes to embedded GitHub actions), you can useactto 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.github/workflows/to replace yourMakefile!
[!TIP] Now Manage and Run Act Directly From VS Code! Check out the GitHub Local Actions Visual Studio Code extension which allows you to leverage the power of
actto 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 and filesystem are all configured to match what GitHub provides.
Let's see it in action with a sample repo!

Act User Guide
Please look at the act user guide for more documentation.
Support
Need help? Ask in discussions!
Contributing
Want to contribute to act? Awesome! Check out the contributing guidelines to get involved.
Manually building from source
- Install Go (version in
go.mod, currently 1.26.0) - (https://golang.org/doc/install) - Clone this repo
git clone [email protected]:nektos/act.git - Run unit tests with
make test(requires Docker) - Run fast tests without Docker with
make test-fast - Build and install:
make install