Moving Commerce Cloud code repository

[Jeomar]

There is an active exploration of moving a Commerce Cloud code repository from Azure DevOps to Bitbucket. A limitation has been identified in the Cloud Portal—only a single repository can be used across all Commerce environments.

Guidance is needed on how to navigate this limitation within SAP. Ideally, the goal is to update the repository destination for a lower environment first, without affecting the production environment, but this does not currently appear feasible. Shifting repositories between locations and environments seems to be a common need.

Looking for resources that can provide support with this challenge or share how others have approached similar situations?

[kevin_wang9]

Hello,

In my option using single repo is more simplicity. If you expect the new change didn't affect the production environment, you can create the new build and deployment the test build on lower environment firstly, then move it to stage or pro env.

Following document provide some more sample/suggestion regarding using repo for complex project:
https://help.sap.com/docs/SAP_COMMERCE_CLOUD_PUBLIC_CLOUD/1be46286b36a4aa48205be5a96240672/0ce946a6c...

Best regards,

Kevin

[Sam6]

Currently only one repo can be added to commerce cloud portal . This is as per the default product behaviour and best practise as well . 
You can create N number of builds using one repo and then most suitable build can be deployed in any environment as builds are environment independent .
All the builds can be access via cloud portal -> builds section . 
For more information regarding the same please check below documentations - 

Commerce cloud repository .

[geffchang]

Assuming you have access to SAP Support, you should create a SAP Support ticket about your concern.

Personally, I think the current behavior of having 1 respository for all environments (Development, Staging, Production) in the same subscription makes sense. I don't see any good reason to have different repositories for different environments. Would that mean you are copying/pushing code from 1 repository to another? It's a weird workflow. But, anyway, that's just my opinion.