Visual Builder repositories for Fusion Cloud extensions

According to Extension Best Practices (Extension Best Practices);

You should use one project for all of your Oracle Cloud Application extension work, with a different Git repository for each product family (known as a pillar in VB Studio)—one for HCM, one for SCM, and so on.

The pillars SCM and Procurement seem to have an overlap: pages like Requisitions are added as dependencies in both pillars. So if we create 2 repositories: prc_extension.git and scm_extension.git, the developper would be prompted everytime to choose between the 2 workspaces: Workspace PRC and Workspace SCM which could be confusing.

Are we better off creating only using one repo for both procurement and scm extensions?