One Release branch per HCM Module changes.

Summary:

Currently, we are simultaneously implementing redwood customization in our Core HR and Benefits module. We are using a single project then one workspace and branch per each module.

The deployment of the changes to production has different schedules. Benefits changes will be deployed first.

We publish changes to main branch for UAT and at the same time we are keeping Release branch for each module for selectively deploying changes. One release branch for Benefits and one release branch for Core HR.

Question:

Once Benefits UAT is completed, we will deploy the benefits release branch to production first then once core HR is completed, we will deploy the separate core HR release branch to production. Will the Core HR release branch overwrites the changes in Benefits release branch since the changes are separated to two different branches?