From b83edeb9ef98c160583168cf81df46e6de79dfd0 Mon Sep 17 00:00:00 2001 From: Steve Dudenhoeffer Date: Sun, 12 Jul 2026 10:24:00 -0400 Subject: [PATCH] ci: rebuild fork image on main source pushes, not just build-definition edits The merge of the /v1/videos/sync routes produced no image because the push trigger only watched the workflow file and Containerfile. Now any Go/UI/deps change on main rebuilds; docs/config-example edits still don't. (The video-routes image itself was built via manual dispatch, tag prefix v231.) Co-Authored-By: Claude Fable 5 Claude-Session: https://claude.ai/code/session_01AXQxVhXBw8PwFAtsVrXSmj --- .gitea/workflows/build-cuda-image.yml | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/.gitea/workflows/build-cuda-image.yml b/.gitea/workflows/build-cuda-image.yml index 55b72990..b81a9873 100644 --- a/.gitea/workflows/build-cuda-image.yml +++ b/.gitea/workflows/build-cuda-image.yml @@ -17,12 +17,19 @@ on: description: "llama.cpp CUDA server build (base image tag suffix)" required: false default: "b9821" - # Building the build definition itself kicks off a fresh image. + # Any change that lands in the shipped binary or image kicks off a fresh + # build (source, UI, deps, build definition). Docs/config-example edits + # don't. push: branches: [main] paths: - ".gitea/workflows/build-cuda-image.yml" - "docker/fork-cuda.Containerfile" + - "**/*.go" + - "go.mod" + - "go.sum" + - "ui-svelte/**" + - "llama-swap.go" env: REGISTRY: gitea.stevedudenhoeffer.com