fleet-greening-ci-local

What problem does it solve?

Drive a repo's CI to green LOCALLY with Agent-CI (Docker), the local analog of greening-ci. Runs a workflow (or all PR/push workflows) in containers, and on the first paused step reads the failure log, fixes the code locally, and agent-ci retries the SAME paused runner — looping until the run lands green or a wall-clock budget expires. Use to validate a workflow change or a release dispatch BEFORE burning a remote run, to catch a CI failure on your own machine, or as the local pre-flight before republishing-stubs / any remote build-matrix dispatch. Where greening-ci watches GitHub Actions remotely and fixes-then-pushes, this runs in local containers and fixes-then-retries in place — no push, no remote runner minutes.

Core Features & Use Cases

• Local Docker-based execution of CI workflows via Agent-CI to validate changes without remote runners.
• Read failure logs of paused steps, apply fixes locally, and retry the SAME runner until green or budget expiry.
• Use Case: Validate a workflow change or deployment before remote dispatch to avoid wasted minutes on remote runners.

Quick Start

Run the local Agent-CI workflow to reproduce a paused step, fix the failing code, and retry the same runner until the workflow completes green or the budget expires.