A code repository is essential for maintaining a single source of truth for software development, ensuring consistency and traceability across changes from multiple contributors. It enables efficient collaboration, version control, and confident deployment of updates.
The three repos we encounter most
Bitbucket
You can configure your Bitbucket repository to automatically build and deploy an environment when you push code changes. This integration synchronizes your Bitbucket repository with your Adobe Commerce on cloud infrastructure account.
GitHub
The GitHub integration enables you to manage your Adobe Commerce on cloud infrastructure environments directly from your GitHub repository.
GitLab
You can configure a GitLab repository to automatically build and deploy an environment when you push code changes. This integration synchronizes your GitLab repository with your Adobe Commerce on cloud infrastructure account.
How to choose
All three work well. The choice usually comes down to: what’s your team already using? What integrations matter (Jira, Linear, etc.)? What’s your CI/CD pipeline?
If you’re starting fresh, GitHub has the most extensive third-party ecosystem. Bitbucket integrates more naturally with Atlassian tooling. GitLab tends to be preferred by teams that want CI/CD built in rather than separately integrated.
Reference
Adobe Commerce Cloud integrations overview →
Adapted from the Adobe Commerce Primer, slide 35. Last reviewed May 2026.