Multi-stage promotion
Best for: Regulated or larger orgs promoting a release through stages.
Four stages — Dev, QA, Staging, Prod — so a change is promoted through each before it ships. Dev, QA, and Staging track named branches; Prod tracks version tags. Pick this if you have a formal promotion path or compliance gates between environments.
Shape
Dev → branch develop QA → branch qa Staging → branch staging Prod → tag v*
What it seeds
Picking this template creates the following environments and slots in your workspace:
| Environment | Slot | Trigger | Pattern |
|---|---|---|---|
| Dev | dev | branch | develop |
| QA | qa | branch | qa |
| Staging | staging | branch | staging |
| Prod | prod | tag | v* |
How updates flow
When something matches a slot's pattern (a push to that branch, a tag with that name, a deployment with that environment), the GitHub webhook fires and the slot card updates in place. Your CI then deploys based on that push and emits deployment_status events, which flow back to update the slot status from Deployingto whatever your workflow ends in. We don't deploy for you.
See Trigger patterns for the full reference, or The board for how to read what you see.
Try it
New workspace? Pick Multi-stage promotion from the picker on /new-workspace. Existing workspace? Go to Settings → Environmentsand use the "Reset to a starting shape" card.