Deployments
A deployment ships a git ref to a game server through a pipeline. You pick the server and the ref; the pipeline does the rest, visibly.
Creating a deployment
From the Game space, a new deployment is two choices: the target server and the git ref to ship — a branch, tag, or commit from one of the repos mapped to that server's modules. The run is pinned to the exact commit SHA it resolved, so what shipped is never ambiguous.
Pipeline runs
Each deployment executes as a pipeline run with named stages, and steps inside each stage, every one carrying its own status. The run records who or what triggered it (the trigger type and ref), when it started, and when it finished. The pipeline detail page follows a run live, stage by stage.
Safety
Pair deployments with snapshots: capture the server before shipping, and a bad deploy is a restore instead of an incident. Because content is git-driven, rolling back is deploying the previous ref.
API surface
# Deployment surface (session cookie or PAT auth)
GET /api/game/pipeline-runs # recent runs with stages/steps
GET /api/game/servers # deployment targets