script/cibuild, script/docker, script/lint and script/test now assign the image tag from script/projectname to tag on its own line before docker build, then pass -t "$tag", "$tag-lint" or "$tag-test". Passed inline, a failing script/projectname did not trip set -e, and the script went on to docker build with an empty or -lint tag. The comment above the line in script/cibuild and script/docker now covers both the version and the tag. Both snippets in prompts/REPO_POLICIES.md show the same form.
Checked with the reproduction from #101 (a script/projectname that only does exit 1) in a scratch copy, with a stand-in docker that only reports being called:
script/cibuild stops with exit 1 before docker build.
script/docker stops with exit 1 before docker build.
script/lint stops with exit 1 before docker build.
script/test stops with exit 1 before docker build.
With the real script/projectname, the tags are prompts, prompts, prompts-lint and prompts-test.
Disclosures:
Judgement call: script/lint and script/test had no such comment; each now has a shorter one above the tag line.
Judgement call: REPO_POLICIES.md gains one sentence stating the own-line rule after "Every docker build in script/ is tagged"; its lint/test snippet shows one tag= line for both builds, though each script assigns its own.
For script/cibuild, the scratch copy also replaced script/bootstrap and script/check with exit 0; otherwise script/check stops first, inside script/test.
Model: opus-5-5
`script/cibuild`, `script/docker`, `script/lint` and `script/test` now assign the image tag from `script/projectname` to `tag` on its own line before `docker build`, then pass `-t "$tag"`, `"$tag-lint"` or `"$tag-test"`. Passed inline, a failing `script/projectname` did not trip `set -e`, and the script went on to `docker build` with an empty or `-lint` tag. The comment above the line in `script/cibuild` and `script/docker` now covers both the version and the tag. Both snippets in `prompts/REPO_POLICIES.md` show the same form.
Checked with the reproduction from https://git.eeqj.de/sneak/prompts/issues/101 (a `script/projectname` that only does `exit 1`) in a scratch copy, with a stand-in `docker` that only reports being called:
- `script/cibuild` stops with exit 1 before `docker build`.
- `script/docker` stops with exit 1 before `docker build`.
- `script/lint` stops with exit 1 before `docker build`.
- `script/test` stops with exit 1 before `docker build`.
- With the real `script/projectname`, the tags are `prompts`, `prompts`, `prompts-lint` and `prompts-test`.
Disclosures:
- Judgement call: `script/lint` and `script/test` had no such comment; each now has a shorter one above the tag line.
- Judgement call: `REPO_POLICIES.md` gains one sentence stating the own-line rule after "Every `docker build` in `script/` is tagged"; its lint/test snippet shows one `tag=` line for both builds, though each script assigns its own.
- For `script/cibuild`, the scratch copy also replaced `script/bootstrap` and `script/check` with `exit 0`; otherwise `script/check` stops first, inside `script/test`.
Model: opus-5-5
script/cibuild, script/docker, script/lint and script/test passed the
tag from script/projectname inline to docker build, where a failing
command substitution does not trip set -e. Each now assigns it to `tag`
on its own line first, so the script stops where script/projectname
fails. The comment above it says why; the REPO_POLICIES.md snippets show
the same form.
Model: opus-5-5
Judgement call: the script/docker and script/cibuild snippet in prompts/REPO_POLICIES.md still differs from those scripts in its comment wording and in calling script/projectname rather than "$SCRIPT_DIR/projectname", as it did before this change; I did not count it, because the policy says the scripts are identical across repositories, not that the snippet is a copy of them.
Model: opus-5-5
PASS: this meets https://git.eeqj.de/sneak/prompts/issues/101 and its plan.
Judgement call: the `script/docker` and `script/cibuild` snippet in `prompts/REPO_POLICIES.md` still differs from those scripts in its comment wording and in calling `script/projectname` rather than `"$SCRIPT_DIR/projectname"`, as it did before this change; I did not count it, because the policy says the scripts are identical across repositories, not that the snippet is a copy of them.
Model: opus-5-5
clawbot
merged commit b09fff488b into next2026-10-06 02:52:24 +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.
script/cibuild,script/docker,script/lintandscript/testnow assign the image tag fromscript/projectnametotagon its own line beforedocker build, then pass-t "$tag","$tag-lint"or"$tag-test". Passed inline, a failingscript/projectnamedid not tripset -e, and the script went on todocker buildwith an empty or-linttag. The comment above the line inscript/cibuildandscript/dockernow covers both the version and the tag. Both snippets inprompts/REPO_POLICIES.mdshow the same form.Checked with the reproduction from #101 (a
script/projectnamethat only doesexit 1) in a scratch copy, with a stand-indockerthat only reports being called:script/cibuildstops with exit 1 beforedocker build.script/dockerstops with exit 1 beforedocker build.script/lintstops with exit 1 beforedocker build.script/teststops with exit 1 beforedocker build.script/projectname, the tags areprompts,prompts,prompts-lintandprompts-test.Disclosures:
script/lintandscript/testhad no such comment; each now has a shorter one above the tag line.REPO_POLICIES.mdgains one sentence stating the own-line rule after "Everydocker buildinscript/is tagged"; its lint/test snippet shows onetag=line for both builds, though each script assigns its own.script/cibuild, the scratch copy also replacedscript/bootstrapandscript/checkwithexit 0; otherwisescript/checkstops first, insidescript/test.Model: opus-5-5
PASS: this meets #101 and its plan.
Judgement call: the
script/dockerandscript/cibuildsnippet inprompts/REPO_POLICIES.mdstill differs from those scripts in its comment wording and in callingscript/projectnamerather than"$SCRIPT_DIR/projectname", as it did before this change; I did not count it, because the policy says the scripts are identical across repositories, not that the snippet is a copy of them.Model: opus-5-5