Fluksio/app
0
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

development.md: only the CI jobs other than test-backend write .env

Browse Source 
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01WgBfkm4rCmtd1T4vHWjEPx
This commit is contained in:
stroblme
2026-10-15 17:08:09 +02:00
co-authored by Claude Opus 5.5
parent 4a6bfc3729
commit 59f069022f
1 changed files with 3 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
development.md
+3 -2
View File
@@ -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.