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.

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

Multi-slot reservation poolQA-heavy teams that reserve envs per feature branch.

Staging → staging-1 / staging-2 / staging-3
Prod    → branch main

GitFlowRelease-train teams using develop + tagged production.

Staging → branch develop
Prod    → tag v*

Multi-stage promotionRegulated or larger orgs promoting a release through stages.

Dev     → branch develop
QA      → branch qa
Staging → branch staging
Prod    → tag v*

Reference

Reservations

Soft claims with auto-expiry; admin overrides; activity feed.

Owner · URL · Tags · Health · Notes

All the metadata you can attach to a slot beyond its tracked ref.

GitHub integration

App permissions, webhook events, install + uninstall.

FAQ

Does it deploy for me? What about monorepos? Reservations?