From 411bff8724a7270be52054b44978da3818fa7a74 Mon Sep 17 00:00:00 2001 From: Oliver Rieger Date: Tue, 4 Aug 2026 14:50:33 +0200 Subject: [PATCH] Describe the two bells that actually hang there Oliver kept a webhook per branch rather than the single unfiltered one, so the note now says that. The part worth keeping is why a filtered hook's Test Delivery always looks dead. Co-Authored-By: Claude Opus 5 --- HANDOFF.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/HANDOFF.md b/HANDOFF.md index 6f65f3b..88baf31 100644 --- a/HANDOFF.md +++ b/HANDOFF.md @@ -27,9 +27,9 @@ the primary target. branch `staging`, same Dockerfile). Test there first, then merge to `main` for the testteam. The branch carries NO diff against main, so it fast-forwards and merges freely — keep it that way. A subdomain, not a subfolder, so staging gets its own origin and can't stomp the prod localStorage. - ONE Gitea webhook serves both, with NO branch filter: Coolify's `/webhooks/source/gitea/events/manual` - matches the resource by repo **and branch**, so a filter would just stop staging deploying. Its - "Test Delivery" button can never work — Gitea fakes a push on the default branch. Push to test. + Two Gitea webhooks, branch-filtered `main` and `staging`, both hitting the same Coolify URL (it + matches the resource by repo AND branch). A filtered hook's "Test Delivery" always looks dead — + Gitea fakes a push on the default branch and its own filter drops it. Push if you want to test. - **Oliver edits files himself** (tuning values, sometimes sprites). ALWAYS Read current file state before editing; never assume your last version is what is on disk.