Each customer workspace will map to a private repository under your GitHub organization. The on-disk layout uses a dedicated top-level folder so it stays distinct from arbitrary application code:
repo/
eltpulse/
pipelines/
my_pipeline/
pipeline.py # or replication.yaml
config.yaml
eltpulse_workspace.yaml # optional per-repo aggregate (future)Generated eltpulse_workspace.yaml (stored alongside definitions in the app) describes scheduling hints, retries, and a logical code location for automation — consumable by eltPulse or by an external orchestrator (Airflow, Prefect, etc.) if you prefer to run triggers outside our control plane.
Automated commits from the app into managed repos are in development. Today, use Code in the builder to copy files into the repo your runners use.