Celes Renata
ebea70573b
- Repository structure for all services, infra, lakehouse, dashboards - K8s manifests targeting stonks-oracle namespace with GHCR images - Ingress via Traefik with ca-issuer TLS for internal services - ConfigMap wired to existing cluster services (pg, redis, minio, ollama) - GitHub Actions workflow for lint, test, multi-service container builds - Dockerfile with build-arg CMD per service - Makefile for local build/push/deploy - Steering rules for TDD workflow, K8s conventions, project context - Agent hooks for lint-on-save, test-on-save, k8s-validate, phase-commit - Ruff linter config, all lint issues fixed - 14 passing tests for schemas, config, redis keys - PostgreSQL migrations, Trino catalogs, Superset config, MinIO lifecycle
17 lines
677 B
Markdown
17 lines
677 B
Markdown
---
|
|
name: Run Tests on Save
|
|
description: Automatically run relevant tests when a Python service file is saved
|
|
version: "1.0"
|
|
trigger:
|
|
type: onSave
|
|
filePattern: "services/**/*.py"
|
|
---
|
|
|
|
When a Python file under `services/` is saved:
|
|
|
|
1. Identify which service module was modified (e.g. `services/ingestion/worker.py` → `ingestion`)
|
|
2. Look for corresponding tests in `tests/` matching the service name
|
|
3. Run `pytest tests/test_{service_name}*.py -x --tb=short -q` if test files exist
|
|
4. If no specific test file exists, run `ruff check` on the modified file to catch syntax/lint issues
|
|
5. Report results concisely — only show failures or a one-line success confirmation
|