Best Practices for Managing Redwood Imp. Across Multiple Modules Using Separate Branches and W.Space

Summary:

Content (please ensure you mask any confidential information):

Hello everyone,

We are currently implementing Redwood on the Core HR module for our client and have some questions regarding the management of changes.

Here is the context:
Once workspaces withseparate branches have been created, whenever changes are made in therespective workspaces, a git push is performed followed by a merge request fromthe respective separate branches into the main branch. This process helpspreserve the separation of customisations by module and keeps the main branchup to date in the testing environment.

For productionmanagement, we have planned to continue using merge requests to progressivelyupdate the production git repository with validated customisations as needed.