Documentation
StagingReservation docs
StagingReservation is the shared source of truth for your team's staging environments. It listens to your GitHub activity and reflects which branch, tag, or deployment is on each slot — in real time, in one place. It never deploys for you; your existing CI does that.
Get going
Getting started
Install the GitHub App, connect a repo, pick a workflow.
Pick a workflow
Four templates — single staging, reservation pool, trunk + preview, GitFlow.
The board
What each slot card shows; status semantics; manual override.
Trigger patterns
branch, tag, deployment — and the glob syntax for each.
Workflows at a glance
Pick the shape closest to how your team ships. You can change it later in Settings → Environments.
Multi-slot reservation poolQA-heavy teams that reserve envs per feature branch.
Staging → staging-1 / staging-2 / staging-3 Prod → branch main
Single stagingSolo or pre-PMF teams shipping from main.
Staging → branch main Prod → branch main
Trunk-based with previewModern trunk teams with per-PR preview environments.
Preview → branch pr-* Prod → branch main
GitFlowRelease-train teams using develop + tagged production.
Staging → branch develop Prod → tag v*