Branch and environment operations
Developers and release engineers managing builds across production, staging, and development.
Understand how production, staging, and development map to Git branches, and how to bootstrap, deploy, rebuild, and detach pipeline branches safely.
Each environment points at a pipeline branch on GitHub. Production follows your repo default; staging and development are mapped explicitly and consume non-production plan capacity.
4 sections4 key takeaways3 related guides
Quick highlights
Each environment points at a pipeline branch on GitHub. Production follows your repo default; staging and development are mapped explicitly and consume non-production plan capacity.
Start with the environment model and mapping rules before running bootstrap or deploy-from-ref — incorrect mappings are the leading cause of builds targeting the wrong code.
What you will learn
- Three environments — production, staging, development — with distinct branch mappings.
- Bootstrap and deploy-from-ref create or move pipeline branches; rebuild queues work on the current mapping.
- Detach removes tnc-sh mapping (and optionally the pipeline branch) without touching production’s default branch.
- Staging requires plan support; managed hosting unlocks the standard rebuild/deploy UI.
Sections in this guide