nektos/act
Run your GitHub Actions locally π
Build with Backblaze B2
SDKs, agent skills, IDE extensions, and reference pipelines from Backblaze Labs. All open source.
Loading star history...
Where it stands
Rank, growth pace and release cadence relative to everything GStars tracks.
Ranks #6 among DevOps repositories ranked this week, and #10 over the last 30 days; #140 of 163 repositories with measured growth this week (top 86%).
This week's +109 stars is ahead of its 30-day pace of about +81 per week.
5 releases in the last 90 days, the latest 6 days ago, with 204 contributors on GitHub.
Use Cases & Benefits
- Runs GitHub Actions workflows locally using Docker to simulate GitHub's environment and filesystem.
- Provides fast feedback by allowing developers to test and debug GitHub Actions without pushing commits.
- Use for validating and debugging CI/CD workflows before committing changes to a remote repository.
- Use for replacing Makefiles by running local task automation defined in GitHub Actions workflows.
- Use for integrating local GitHub Actions testing directly within Visual Studio Code via an extension.
Should you depend on it?
License terms, project hygiene and risks, from GitHub metadata and GStars' snapshots.
License
MIT
Permissive: commercial use, modification and redistribution are allowed with attribution.
Community files
- README: present
- Contributing guide: present
Watch-outs
No watch-outs from GStars' checks.
General guidance from repository metadata, not legal advice. How we score
From the README
"Think globally,
actlocally"Run your GitHub Actions locally! Why would you want to do this? Two reasons:
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.When you run
actit 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!
Please look at the act user guide for more documentation.
Daily snapshots
Stars gained per day, and how forks and open issues moved, from GStars' daily snapshots
+1,077 stars over 84 days across 26 snapshot days; best day +31 on Sep 14.
Forks
2.1K+115
Open issues
386+24
Compared with peers in DevOps
Fastest-growing repositories GStars tracks in this cohort for the week of Nov 8, by 7-day star growth
| Repository | Stars | +7d | Health | Last release |
|---|---|---|---|---|
| milind-soni/OpenMausBot | 20.6K | +8.4K | 75 | today |
| DuarteSantos8/openGym | 20.8K | +1.7K | 75 | 7 days ago |
| superplanehq/superplane | 9.8K | +1.0K | 75 | 13 days ago |
| elie222/rakazo | 7.8K | +958 | 75 | today |
| AstrBotDevs/AstrBot | 46.6K | +774 | 75 | 10 days ago |
| nektos/act | 72.6K | +109 | 75 | 6 days ago |
| Category median | 20.6K | +1.0K | 75 | β |
Discover Repositories
Search across tracked repositories by name or description