what is ciwalk fr?

ciwalk lets developers run their GitHub Actions CI pipeline locally in Docker and actually debug it, instead of the usual cycle of editing YAML, committing, pushing, waiting, and reading logs to guess what went wrong. It can pause at any step, either automatically on failure or at a chosen breakpoint, and drop the user into a live interactive shell running inside the exact same container as that step, with the same environment and working directory. From there the user can inspect files, fix whatever is broken, then exit and choose to retry the step, continue to the next one, or abort the run entirely. Other similar tools that run GitHub Actions locally tend to be all or nothing, but ciwalk keeps the container alive after a failure so the user can interact with it directly, and the mounted workspace is live on the host machine too, so changes made in the shell are visible outside the container as well. Even if the user chooses to continue past a failed step, the overall run still exits with a non-zero status so the failure is not silently hidden. Installation requires Python 3.11 or newer and a running Docker daemon. It can be installed from PyPI, directly from GitHub, from a local clone for development, or as a standalone platform binary from GitHub Releases that does not require installing Python packages, though Docker is still needed either way. The tool currently supports a limited subset of GitHub Actions syntax: single job runs on an Ubuntu based image, basic steps with run, name, env, and working-directory fields, the checkout action through a local bind mount rather than a network clone, and simple input and environment variable substitution. Anything outside that subset, such as matrix builds, secrets, the full GitHub expression language, or jobs with dependencies between them, is explicitly rejected or skipped with a loud, non-zero exit rather than silently passing. The project is released under the MIT license.