greening-ci-local

Run GitHub Actions workflows locally in Docker to validate CI changes by executing them in containers and automatically retrying paused steps until the run passes or a time budget expires. This enables fast feedback without using remote runners.

Yes, you can validate a single workflow file locally before pushing to remote CI. The tool runs the specified workflow in local containers, allowing you to preflight changes and catch failures on your own machine without burning remote runner minutes.

The best way to automatically fix and retry paused CI steps locally is using an agent that reads failure logs, modifies code in place, and retries the same paused runner in Docker. This loops until the workflow lands green or a wall-clock budget is reached.

Yes, local CI execution with Docker avoids pushing code to remote repositories. It runs workflows in local containers and fixes then retries steps in place, ensuring no code is pushed and no remote runner minutes are consumed during validation.

You can set a wall-clock budget for local workflow validation loops to constrain execution time. The tool automatically stops retrying paused steps and terminates the local run when this budget expires, preventing infinite loops.

Use local Docker containers instead of remote GitHub Actions runners for CI preflight to get deterministic execution and fast feedback without consuming remote runner minutes. It allows you to catch and fix failures on your local machine before dispatching a remote build.