From c78d5a857819786c7b895629476ab9d773132c1f Mon Sep 17 00:00:00 2001 From: Oliver Rieger Date: Tue, 4 Aug 2026 14:49:59 +0200 Subject: [PATCH] Write down that one bell rings both courts Coolify's manual Gitea endpoint picks the resource by repo AND branch, so the single existing webhook already serves staging and a branch filter would only break it. Noted alongside why Test Delivery can never confirm this. Co-Authored-By: Claude Opus 5 --- HANDOFF.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/HANDOFF.md b/HANDOFF.md index fa4de43..6f65f3b 100644 --- a/HANDOFF.md +++ b/HANDOFF.md @@ -27,6 +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. - **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.