act: Run your GitHub Actions locally.
What problem it solves
Workflow changes are otherwise tested by repeatedly committing and pushing changes before they can run. Developers also need a way to reuse workflow-defined tasks locally instead of maintaining separate command sequences.
Key features
Workflow Discovery — Reads GitHub Actions definitions from `.github/workflows/` and determines which actions need to run.
Source: README, cmd
Container-Based Execution — Uses the Docker API to pull or build workflow images, derive the execution path from dependencies, and run each action in a container.
Source: README, go.mod
GitHub-Compatible Environment — Configures environment variables and the filesystem to match the environment provided by GitHub.
Source: README
Local Task Runner — Allows workflow-defined actions to be used locally in place of a separate Makefile.
Source: README, Makefile
Source Build and Test Workflow — Documents manual setup for building from source and provides separate test commands for Docker-backed and Docker-free runs.
Source: README
Who it may suit
This may suit developers who maintain GitHub Actions workflows and want to test workflow changes or run workflow-defined tasks locally.
Topics to discuss
Which local environment details should be matched most closely when testing GitHub Actions workflows?
How should Docker-backed and Docker-free test workflows be maintained as the project evolves?
Which additional local task-runner integrations would be useful to contributors?
Written by ReadmeX AI from the project's README, source and public GitHub data; it may contain mistakes.
Read the original README https://github.com/nektos/act#readme
ReadmeX opened this community for a trending project; it is not run by the project. Maintainers can claim it from the community page.
Comments
…