max / alloy_tui

Disable sr.ht auto-CI while iterating locally Rename .builds/ to builds.disabled/ so sr.ht stops auto-running the smoke test on every push. Local podman builds are the iteration loop until the Containerfile is known good; renaming the directory back to .builds/ re-enables sr.ht CI in one commit.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Author: Max Johnson <me@maxj.phd> · 2026-07-04 14:57 UTC

Signed with PGP, not checked

Commit: 8d0bca65a0662f9a2791c4fd67cae2c2f8f0f4d3

Parent: 0900bc1

2 files changed, +4 insertions, -2 deletions

M docs/IMAGE.md +4 -2

			@@ -42,9 +42,11 @@
42	42
43	43		Primary remote. Alloy is source-hosted on sr.ht for the same reasons the rest of Make Creative's public work is: independence from big-tech-monopoly infrastructure at the layer where users install software. `srht` is a canonical remote for Alloy, not a backup.
44	44
45		-	### CI: `builds.sr.ht`
	45	+	### CI: `builds.sr.ht` (disabled during local-iteration phase)
46	46
47		-	sr.ht ships Fedora build VMs with `dnf`, `podman`, `buildah`, `skopeo` preinstalled. Fits Alloy's build needs without additional plumbing. The build file lives at `.builds/alloy-image.yml` in the repo root.
	47	+	sr.ht ships Fedora build VMs with `dnf`, `podman`, `buildah`, `skopeo` preinstalled. When ready, the build file at `.builds/alloy-image.yml` triggers on every push.
	48	+
	49	+	Current state: the build file lives at `builds.disabled/alloy-image.yml` — parked outside the `.builds/` path sr.ht auto-runs, so no CI resources are consumed while the Containerfile is being iterated locally. Rename the directory back to `.builds/` and push to re-enable.
48	50
49	51		### Registry: `quay.io` (deferred until distribution starts)
50	52

R .builds/alloy-image.yml → builds.disabled/alloy-image.yml