Files
sonar-test-nest2/README.md
andrej 328de59412
Some checks failed
SonarQube Analysis / Build, Test & Analyse (pull_request) Failing after 51s
Integration Test / Platform Conformance (pull_request) Failing after 4s
Integration Test / Unit Tests + Container Smoke (pull_request) Has been skipped
Updated readme.md
for SONAR test
2026-05-11 12:43:13 +00:00

24 lines
881 B
Markdown

# sonar-test-nest2 v2
> **System-of-Record branch** — application code lives on `dev`.
| Branch | Purpose |
|-----------|---------|
| `dev` | Inner loop — push freely, deploys to dev env automatically |
| `staging` | Staging env — promoted from dev via PR (CI gate + 1 approval) |
| `prod` | Production — promoted from staging via PR (CI gate + 1 approval) |
| `main` | System of record — receives merges from prod after releases |
## Platform CI/CD
Workflows in `.gitea/workflows/` are **runtime-agnostic** — they read
`.platform/config.yaml` at run-time to determine build toolchain, container
port, and health endpoint. No workflow files need updating when this service
is migrated to a different runtime.
| Config key | Value |
|------------|-------|
| `runtime` | `typescript-nestjs` |
| `health_path` | `/health` |
| `container_port` | `3000` |