Waters ChurchandClaude Opus 5 af97626b12 Fix the build workflow's YAML so it actually runs ...

The alert steps passed their message body as a bare multi-line argument starting
at column 0. That ends the YAML block scalar, which makes the whole file invalid:
"a multiline key may not be an implicit key". Gitea still listed the workflow as
active and simply never created a run for it — no error anywhere, which is why two
pushes appeared to do nothing.

The bodies are built with indented heredocs now, so every line stays inside the
block scalar. Validated by parsing the file rather than by eye; a workflow that is
registered but silently never triggers looks exactly like one that works.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

2026-09-24 15:39:08 -04:00

..

build-apps.yml

Fix the build workflow's YAML so it actually runs

2026-09-24 15:39:08 -04:00

deploy.yml

Drop the duplicate docker.sock mount from the deploy job

2026-09-24 14:02:51 -04:00