Expand my Community achievements bar.

SOLVED

Edge Delivery services branching strategy

Avatar

Level 2

Adobe documentation for Edge Delivery services mentioned about merging code into the main branch. Should all pull requests go straight to the main branch for the live site, or can we create separate develop and release branches like in typical AEM projects?

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

Hi @HariPr6 
You can contact adobe directly to clarify that.

 

But Adobe suggested to use different git repo for each environment and merge to main branch and then just create a PR with fork to STAGE or PROD but now they have introduced repoless there you can use same code with different website, maybe this can help to achieve what you are mentioning using dev and release branches in typical development 

https://www.aem.live/docs/repoless 

 



Arun Patidar

View solution in original post

1 Reply

Avatar

Correct answer by
Community Advisor

Hi @HariPr6 
You can contact adobe directly to clarify that.

 

But Adobe suggested to use different git repo for each environment and merge to main branch and then just create a PR with fork to STAGE or PROD but now they have introduced repoless there you can use same code with different website, maybe this can help to achieve what you are mentioning using dev and release branches in typical development 

https://www.aem.live/docs/repoless 

 



Arun Patidar