wuwi/splatter-tennis
1
0 Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Write down that one bell rings both courts

Browse Source 
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 <noreply@anthropic.com>
This commit is contained in:
wuwiandClaude Opus 5 committed 2026-08-04 14:49:59 +02:00
1 parent 4f49a0b4e1
commit c78d5a8578
1 file changed
+3
Download Patch File Download Diff File Expand all files Collapse all files
HANDOFF.md
+3
View File
@@ -27,6 +27,9 @@ the primary target.
branch `staging`, same Dockerfile). Test there first, then merge to `main` for the testteam. 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. 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. 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 - **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. before editing; never assume your last version is what is on disk.