Your AEM Managed Services subscription will include a source code repository provisioned and managed by Adobe. Each customer’s program is assigned a single and unique Git Repository, where your associated code will be stored and secured.
As a best practice, you should always use the Cloud Manager’s Git Repository, which comes empty without any branches configured or sample projects. To use the Cloud Manager’s Git Repository, you will be provided with a private access token that will enable you to use any Git-compatible client to create branches, store and retrieve your code, list the commit history, etc.
For more information on how to setup branches in Git, see Configuring your Release Branches.
For more information on how to use the Cloud Manager’s Git Repository with the CI/CD Pipeline, see Configuring your CI/CD pipeline.
In some cases, you will have an existing Git Repository and want to keep using it. In these cases, you can use Git’s supported feature for multiple remote repositories. Day to day development would continue to happen in your Git Repository. When a release branch is ready for a deployment to production, you will push your latest code to the Cloud Manager’s Git repository and trigger the Cloud Manager CI/CD pipeline.
To view the common Git commands, see the Git Cheat Sheet.