The canonical REPO_POLICIES.md, re-vendored under #196, says the Gitea workflow runs script/cibuild on push and checks out the repo as its only other step.
pixa's .gitea/workflows/check.yml also runs script/docker-smoke, added under #111 so that CI starts the image and waits for its healthcheck. Dropping the step loses that check from CI; keeping it needs the canonical policy changed. That choice is the owner's.
Model: opus-5-5
The canonical `REPO_POLICIES.md`, re-vendored under https://git.eeqj.de/sneak/pixa/issues/196, says the Gitea workflow runs `script/cibuild` on push and checks out the repo as its only other step.
pixa's `.gitea/workflows/check.yml` also runs `script/docker-smoke`, added under https://git.eeqj.de/sneak/pixa/issues/111 so that CI starts the image and waits for its healthcheck. Dropping the step loses that check from CI; keeping it needs the canonical policy changed. That choice is the owner's.
Model: opus-5-5
clawbot
self-assigned this 2026-10-04 22:29:51 +02:00
Question for @sneak: should pixa's CI keep its script/docker-smoke step?
The canonical REPO_POLICIES.md says the Gitea workflow checks out the repo and runs script/cibuild, nothing else. pixa's workflow also runs script/docker-smoke, which starts the built image and waits for its health check to report healthy (added under #111). That catches an image that builds but does not start, which script/cibuild alone does not.
Keep the step, and let the canonical policy allow a repo to add a step after script/cibuild that starts the image (recommended: it is the only CI check that the container actually runs, and the policy change lives in sneak/prompts).
Drop the step to match the policy as it stands; pixa then has no CI check that the image starts.
Nothing else waits on this.
Model: opus-5-5
Question for @sneak: should pixa's CI keep its `script/docker-smoke` step?
The canonical `REPO_POLICIES.md` says the Gitea workflow checks out the repo and runs `script/cibuild`, nothing else. pixa's workflow also runs `script/docker-smoke`, which starts the built image and waits for its health check to report healthy (added under https://git.eeqj.de/sneak/pixa/issues/111). That catches an image that builds but does not start, which `script/cibuild` alone does not.
- Keep the step, and let the canonical policy allow a repo to add a step after `script/cibuild` that starts the image (recommended: it is the only CI check that the container actually runs, and the policy change lives in `sneak/prompts`).
- Drop the step to match the policy as it stands; pixa then has no CI check that the image starts.
Nothing else waits on this.
Model: opus-5-5
clawbot
removed their assignment 2026-10-04 22:42:56 +02:00
sneak
was assigned by clawbot2026-10-04 22:42:56 +02:00
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.
The canonical
REPO_POLICIES.md, re-vendored under #196, says the Gitea workflow runsscript/cibuildon push and checks out the repo as its only other step.pixa's
.gitea/workflows/check.ymlalso runsscript/docker-smoke, added under #111 so that CI starts the image and waits for its healthcheck. Dropping the step loses that check from CI; keeping it needs the canonical policy changed. That choice is the owner's.Model: opus-5-5
Question for @sneak: should pixa's CI keep its
script/docker-smokestep?The canonical
REPO_POLICIES.mdsays the Gitea workflow checks out the repo and runsscript/cibuild, nothing else. pixa's workflow also runsscript/docker-smoke, which starts the built image and waits for its health check to report healthy (added under #111). That catches an image that builds but does not start, whichscript/cibuildalone does not.script/cibuildthat starts the image (recommended: it is the only CI check that the container actually runs, and the policy change lives insneak/prompts).Nothing else waits on this.
Model: opus-5-5