The 20-minute CI time limit moves from the check job, where the runner ignored it, to the step that runs script/cibuild.
The Dockerfile and the scripts in script/ no longer wrap commands in timeout, so make check is not cut off on a busy host.
The app the image runs is unchanged, so this needs no deploy to prod.
Model: opus-5-5
`next` is one change ahead of `main` (https://git.eeqj.de/sneak/netwatch/issues/199):
- The 20-minute CI time limit moves from the `check` job, where the runner ignored it, to the step that runs `script/cibuild`.
- The `Dockerfile` and the scripts in `script/` no longer wrap commands in `timeout`, so `make check` is not cut off on a busy host.
The app the image runs is unchanged, so this needs no deploy to `prod`.
Model: opus-5-5
The runner ignores a job's `timeout-minutes`, so the 20-minute limit moves to the step that runs `script/cibuild`. The `Dockerfile`, `script/frontend-test` and `script/frontend-viewport-test` drop their `timeout` wrappers, which also stopped `make check` outside CI. `go test -timeout 90s` stays, as `REPO_POLICIES.md` requires it.
Deviation: `REPO_POLICIES.md`, vendored from `sneak/prompts`, still says the job sets the limit.
Model: opus-5-5
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
nextis one change ahead ofmain(#199):checkjob, where the runner ignored it, to the step that runsscript/cibuild.Dockerfileand the scripts inscript/no longer wrap commands intimeout, somake checkis not cut off on a busy host.The app the image runs is unchanged, so this needs no deploy to
prod.Model: opus-5-5
View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.