Feature branches with different lifecycles

[ThomasBuchinger]

As a developer in Automate implementing a brand new feature, I might want to have an additional feature-branch, implementing a sub-feature (e.g. extending existing library code vs the overall workflow implementation) with a different lifecycle. At the same time, the main workflow adds a new functionality to the same library code.

Example

branch1: Extend IPAM Lib with DNS
/Integration/IPAM/MyIPAM.class/request_ip_address  # Add ability to register DNS with IP

branch2: Main AwsomeService workflow
/Integration/IPAM/MyIPAM.class/request_ip_address  # Add some logic to specific to AwsomeService
/Service/Provivsion/StateMachines/ServiceTemplate.class/AwsomeService
/Integration/AwsomeService/StateMachines/Provision.class/register_ip
/Integration/AwsomeService/StateMachines/Provision.class/method1

In a normal scenario, branch1 would be merged into branch2 and could be worked on, until branch1 is merged into master, however due to shadowing in ManageIQ Domains, this is not possible to do it that way.