An experimental tool that runs GitHub Actions workflows locally using Docker containers.
wflow is an experimental tool that runs GitHub Actions workflows locally using Docker containers. It allows developers to test and debug their GitHub Actions workflows on their own machines without needing to push changes to GitHub, providing a faster feedback loop and reducing cloud resource consumption.
Developers and DevOps engineers who use GitHub Actions for CI/CD and want to test workflows locally before committing changes.
It offers a local simulation of GitHub Actions, enabling rapid iteration and debugging without relying on cloud infrastructure, which can save time and reduce costs.
🐆 EXPERIMENTAL -- Runs GitHub Actions workflows locally (local) -- Don't run your YAML like a 🐪
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Runs GitHub Actions workflows locally without pushing to GitHub, enabling rapid iteration and debugging, as mentioned in the philosophy to reduce cloud dependency.
Uses Docker containers to simulate the GitHub Actions environment, ensuring isolation and consistency similar to cloud VMs, as described in the 'How It Works' section.
Streams logs from Docker containers via WebSockets to a local UI, allowing developers to monitor execution in real-time for immediate feedback, a key feature highlighted in the README.
Creates isolated workspaces for each job with steps operating on the same workspace, mimicking GitHub's behavior to prevent cross-contamination, as explained in the workspace management feature.
Only supports Docker-based actions, not JavaScript-based ones, which restricts compatibility with many existing GitHub Actions, as admitted in the 'Currently supported' section with 'PRs welcome' for JavaScript actions.
Lacks support for critical workflow elements like event triggers (`on`), scheduled jobs, and job strategies, making it incomplete for complex pipelines, as listed under 'Not yet supported'.
Marked as experimental with potential bugs and breaking changes; the README notes 'The UI needs some work,' indicating it's not polished or reliable for consistent use.