Troubleshooting

Troubleshooting

no GitHub token found

gh auth login          # or: export GITHUB_TOKEN=…
gh auth refresh -s repo   # private repositories

could not start act

reenact drives act; install it and make sure it is on PATH, or point at it with --act /path/to/act.

Cannot reproduce this job: non-linux

Working as intended — see Scope and limits. The report above that line still tells you the commit, the matrix leg and which step failed.

A step fails locally that passed on CI

Almost always the image. GitHub's runners have far more preinstalled than the default act image:

reenact <url> --image full

That image is large (~60 GB unpacked) but matches CI far more closely. The fidelity report names the image it chose and why.

the input device is not a TTY

You piped or redirected stdin. reenact detects this and asks Docker for a non-interactive session, so this should not happen — if it does, please open an issue with the command you ran.

The container is gone but the workspace is still there

Only happens if the process was killed outright (kill -9, a closed pipe on an older version). Remove it with the command reenact prints, which works even for files the container wrote as root:

docker run --rm -v /tmp/reenact-…:/x alpine rm -rf /x

I want to see what act is actually doing

reenact <url> --verbose

The raw output goes to a log file in the workspace regardless; the path is printed on failure.

I want to see everything without running anything

reenact <url> --dry-run

Prints the generated workflow and the exact act command. Clones nothing, runs nothing, and never writes your secrets to disk.