- Get Started
- Functionality
- Learning
- Extension
- Dev Tooling
- APIs
- Releases
Changed on:
9 Nov 2026
| Branch | Purpose | Pipeline behavior |
`feature/*`, `fix/*` | One change each, short-lived | Build and test only |
`dev` | Integration branch | Merged through a merge queue; each merge builds, tests and deploys to the dev account |
`main` | Release candidates | Each merge builds, tests and tags the commit with the build number |
`release/<tag>` | One per release, cut from a tag | Builds and deploys to UAT on manual trigger, then to production on a separate manual trigger |
`dev` and `main`. The queue rebuilds each change on top of the latest target branch before merging. Without it, two PRs that each pass on their own can break together, and the first anyone hears of it is a broken dev account.Deploy only from shared branches. Feature branches build and test but never deploy, so the dev account always reflects `dev`, the one branch that everyone's work has been merged into.One person deploys to an environment at a time. Bitbucket deployment environments serialize deploys to the same environment. Leave this on.`main` tags the commit with the build number. The tag is also the build identifier that `build-module.sh` appends to the module version, so the tag, the module version and the deployed version all match.`release/<tag>` from that commit.`dev` first and are then cherry-picked onto the release branch. Never fix only the release branch, or the next release will bring the defect back.1gitGraph
2 commit
3 branch dev
4 branch feature/order-split
5 commit
6 commit
7 checkout dev
8 merge feature/order-split tag: "deploy → dev"
9 checkout main
10 merge dev tag: "412"
11 branch release/412
12 commit tag: "deploy → UAT → prod"1# releases/412.yaml
2release: "412"
3commit: 3f9c2e1
4module:
5 name: ACME
6 version: 1.0.412
7reference_modules:
8 fluent-commerce/core: 2.2.1
9mystique:
10 acme-mystique-plugin: 1.4.0
11notes: CHANGELOG.md#412