The fork as branch feature allows you to create a copy of your current workflow at its exact state, enabling you to experiment, test variations, or recover previous versions without impacting your main workflow.
Why use fork as branch
This feature creates an independent copy of your workflow, starting from the specific version or commit you are currently viewing. Use it whenever you want to work on a version of your workflow that is separate from your main work:
Experimental changes: Safely test risky changes or new implementations without affecting the stability of your main branch.
Feature development: Start a new feature development branch from your main workflow so you can work in isolation.
Version recovery: If you are viewing a past version of your workflow in history, you can fork it to create a new branch. This effectively "restores" that old state as the starting point for a new branch.
A/B testing: Create multiple branches from the same source to compare different workflow configurations side-by-side.
Collaboration: Fork someone else's branch to make your own modifications without disrupting their work.
Fork as branch vs. a new branch
While both options create new branches, they serve different purposes:
New branch: Starts a fresh branch from the latest version of your main workflow. Use this when starting new, standard work.
Fork as branch: Creates a branch from the specific commit you are viewing. Use this when you
How to use fork as branch
In your workflow, open the three-dot menu (⋮) within the branch selector and select fork as branch from the dropdown menu. You will be automatically navigated to your new, independent branch.
Key things to know
Independence: Once a branch is forked, it is entirely independent. Changes made in the new branch will not affect the source branch.
Requirements: You must have write permissions for the workflow to use this feature. It is available whether you are working on the main branch or an existing feature branch.