How does the Integration → Staging → Production branch flow work?
Categories:
Adobe Commerce Cloud
ACC enforces a 3-tier git branch strategy by design:
- Integration: ephemeral feature branches per developer/PR. Each push triggers a deploy. Used for PR review.
- Staging: mirrors Production data (sanitised) and infrastructure. UAT happens here.
- Production: live store. Only promotions from Staging are allowed.
Done right, each branch has its own data-bridge so a Staging deploy can be tested against real-shape data without touching Production. We set this up properly on every project.
Was this helpful?