Edge Delivery services branching strategy | Community
Skip to main content
Level 2
September 30, 2024
Solved

Edge Delivery services branching strategy

  • September 30, 2024
  • 1 reply
  • 848 views

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?

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by arunpatidar

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 

 

1 reply

arunpatidar
Community Advisor
arunpatidarCommunity AdvisorAccepted solution
Community Advisor
October 9, 2024

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