What is Allow all branching?

Allow all branching is a Project setting that controls where Team Members can create branched Sites from. By default, Team Members can only branch from your Project's Main Branch. With Allow all branching turned on, Team Members can branch from any Site in your Project, including other branched Sites.

Allow all branching is useful when Team Members need to start their work from a Site in your Project that is not your Main Branch. Two common cases:

• Working in a Project with multiple staging Sites. Your Main Branch can only point at one branch in your Project. With Allow all branching turned on, Team Members can branch from any of your staging Sites, not just the one you set as Main.
• Building on another Team Member's in-progress work. A Team Member is part-way through a longer change, and another Team Member needs to build on their unpublished work. With Allow all branching turned on, the second Team Member can branch from the in-progress Site without waiting for the first Team Member to publish.

When a Team Member branches from a Site that is not your Main Branch, the new branched Site publishes back to that source Site — not to the Main Branch. CloudCannon sets the source Site as the new Site's Publish Branch by default, so you can pull updates from the source as it changes and publish your changes back to it. For more information on the settings CloudCannon applies to new branched Sites, please read our documentation on what Branch Defaults are.

Allow all branching is turned off by default. You can turn it on or off at any time, and existing branched Sites are not affected by the change. For more information, please read our documentation on turning on Allow all branching.