From 59f069022f44a4100b3bc1c2d9b74261c9360e0c Mon Sep 17 00:00:00 2001 From: stroblme Date: Thu, 15 Oct 2026 17:08:09 +0200 Subject: [PATCH] development.md: only the CI jobs other than test-backend write .env Co-Authored-By: Claude Opus 5.5 Claude-Session: https://claude.ai/code/session_01WgBfkm4rCmtd1T4vHWjEPx --- development.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/development.md b/development.md index cac3c93..797e7a5 100644 --- a/development.md +++ b/development.md @@ -184,8 +184,9 @@ contract between the two frontends, and that target is the only thing checking i ## CI -`.gitea/workflows/` runs four jobs, each writing `.env` from `.env.example` first: +`.gitea/workflows/` runs four jobs: `test-backend.yml` (pytest on Python 3.12 and 3.14, plus a check that both wheels build), `playwright.yml` (the e2e suite in two shards, one compose project each, the browser loading the SPA from the nginx `frontend` service), `pre-commit.yml` (the hooks above, plus strict mypy, which they do not cover) and -`test-compose.yml` (a smoke test that the production images actually come up). +`test-compose.yml` (a smoke test that the production images actually come up). All but +`test-backend.yml` write `.env` from `.env.example` first. The backend suite needs none.