How can I use act to debug a GitHub Actions workflow locally?
nektos/act
act runs selected GitHub Actions jobs in local containers so engineers can debug workflow changes before pushing them.
Public GitHub facts reviewed Nov 14, 2026. Independent editorial profile; not a sponsored entry.
How is the score calculated?
Calculated on 14.11.2026. Missing public information receives no points. The index does not establish code quality, security, fitness, or future visibility.
What can act help with?
Reproduce a broken dependency install before opening a pull request
Run the failing job against a known image, then compare runtime, package manager, and lockfile behavior with the GitHub-hosted run.
Verify event-driven branch logic with fixtures
Use separate event files for a feature branch and a release branch. Check which build job runs in each case and leave deployments disabled during local testing.
Questions people ask before using act
How can I use act to debug a GitHub Actions workflow locally?
Install act and make sure the supported container engine is running. List jobs for the event that you are troubleshooting and select an owned job that checks or builds the code. Reproduce it with a small local fixture and compare the step where it fails with the hosted log.
Can I run only one CI job from a monorepo?
Pass the workflow file with -W and the target job ID with -j, plus the matching event name. Use list mode to confirm the job is selected. Check whether dependencies pull in additional jobs or need files from a different workspace.
How do I reproduce a pull request bug that depends on the target branch?
Create test JSON with the input fields the workflow actually reads and pass it with -e. Use separate files for the expected run and skip conditions. An empty event object can miss branch logic that is populated on GitHub.
Why does a job work on GitHub but fail locally with a missing tool?
Inspect the chosen container image and find which packages are installed. Add or pin the runtime setup in the workflow where practical. A hosted runner image and a lightweight local image can bring different tooling to the same job.
How should I check matrix jobs without waiting for the full suite?
Run a targeted combination with the relevant language version and architecture values first. Put at least one neighboring combination through the same check when the failure may be version-specific. Leave the full hosted matrix as the merge check.
What is a safe way to exercise release logic in local CI?
Use a trusted workflow in a test repository or branch, keep external publish steps disabled, and use fixture values. Review any checked-out code and third-party actions before execution. Keep production tokens out of the local run and its logs.
Can I use act to confirm GitHub permissions and deployment approvals?
Use the managed runner and configured repository environment for the final permission and approval checks. Consult the project’s unsupported functionality page for platform-specific behavior. Local runs help confirm logic and build steps under the container configuration you chose.
How can my team make local CI results reproducible across laptops?
Agree on a checked-in workflow fixture, a runner image and tested versions for toolchains. Record the event and job command alongside the expected result. Compare ARM and x86 behavior if your team works on both architectures.
Can I ship act with an internal developer toolkit?
The act repository uses the MIT license. Carry forward the copyright and permission notice when redistributing substantial parts of the software, and separately track licenses for the actions and images bundled with your toolkit.
How do act and Playwright work together in a web team?
Playwright checks what happens in the browser, such as successful navigation or form submission. act checks the CI job that prepares dependencies and invokes those tests. Run a browser specification directly for fast debugging, then validate the surrounding workflow when it changes.
What to check before adoption
- Primary language
- Go
- GitHub license field
- MIT
- License according to repository file
- MIT · LICENSE ↗
- Stars / forks in this snapshot
- 72,691 / 2,123
- Last code push
- 14.11.2026
- Self-hostable
- Potentially, verify operating requirements
The local runner differs from managed GitHub runners in supported features, available software, permissions and event payloads. Confirm workflows that publish or need platform-specific behavior on GitHub.
Comparison and original sources
Compared with playwright Use act when the question is how a workflow launches and wires its jobs together. Use Playwright when the question is what a visitor can do in the browser. A single CI workflow can run Playwright as one step.
Documentation and repository data
Compare related projects
lighthouse
GoogleChrome/lighthouse
An automated audit tool for web performance, accessibility, SEO checks, and best practices.
GitHub snapshot 11.11.2026 · Score method on profile
A visual low-code environment for event-driven automations and integrations.
GitHub snapshot 11.11.2026 · Score method on profile
wordpress-develop
WordPress/wordpress-develop
A GitHub mirror of the WordPress core development project.
GitHub snapshot 11.11.2026 · Score method on profile
Back to Open Source Radar
Explore more projects by job, technology, and license.