Expand my Community achievements bar.

Don’t miss the AEM Skill Exchange in SF on Nov 14—hear from industry leaders, learn best practices, and enhance your AEM strategy with practical tips.

Automatic Deletion of Merged Feature Branches from Adobe Git

Avatar

Level 2

8/29/24

Request for Feature Enhancement (RFE) Summary: Automatic Deletion of Merged Feature Branches from Adobe Git
Use-case: We have a sync job that syncs organization-specific branches to Adobe Git. This job performs deployments to AEM Cloud as a Service Dev instances for testing and validation. Once the testing is complete, the corresponding feature branches are merged into the Main branch, which triggers deployment to AEM Cloud as a Service stage/Prod. However, the feature branches are not being deleted from Adobe Git after the merge, leading to clutter and potential confusion.
Current/Experienced Behavior: After merging feature branches into the Main branch, these branches are automatically deleted from our organization’s repository. However, they remain in Adobe Git, which creates unnecessary clutter and can lead to potential errors.
Improved/Expected Behavior: Feature branches should be automatically deleted from Adobe Git once they have been merged into the Main branch, mirroring the behavior in our organization’s repository. This would streamline branch management and ensure consistency across repositories.
Environment Details (AEM version/service pack, any other specifics if applicable): AEM Cloud as a Service / Cloud Manager
Customer-name/Organization name: Allianz Technology
Screenshot (if applicable):  
Code package (if applicable):  
1 Comment

Avatar

Administrator

9/13/24

@shaijuseb 

Thanks for proposing this idea.
This has been reported to the engineering under the internal reference SITES-25120. The product team will triage this request to verify feasibility based on the prioritization model. This post will be updated according to the Jira status.
Status changed to: Investigating