Branches
Designer uses branching for version control, as this allows your teams to work on different pipelines separately from your main branch. We recommend that you develop pipelines in Designer on named development branches, rather than the main branch. Not added a project yet? Read Add project.
Best practice
Choose an appropriate branching strategy for your team based on your development workflow, team size, and collaboration preferences:
- For teams of three or more, a multi-branch strategy like feature branching is recommended. This allows developers to work on individual features in isolation from the main branch. It is particularly useful when multiple developers are working on different aspects of a project simultaneously.
- For smaller teams, consider a trunk-based development strategy—a more streamlined approach to version control that prioritizes simplicity and speed. This workflow is suitable for teams focusing on continuous delivery and rapid iteration. The main branch is kept in a deployable state at all times, ensuring that the latest changes are always ready for production.
For more information, read Matillion's Unlocking Data Productivity DataOps guide.
Add new branch
- In the left navigation, click the Projects icon
. - Select your project.
- Navigate to the Branches tab.
- Click Add new branch.
| Property | Description |
|---|---|
| Branch name | A unique name for the new branch. |
| Branch from | Select which branch to branch from, for example, main. |
| Default environment | Select the environment that this branch will use by default. Not created an environment yet? Read Add environment. |
Click Create to add the new branch, or click Never mind to cancel.
Locate your new branch in the Branches menu and click it to redirect to the Designer.
Manage branches
To edit a branch, click ... for that branch and click Edit branch details.
To delete a branch, click ... for that branch and click Delete branch.
If you use a Matillion-hosted Git repository, deleted branches can't be recovered. You can reuse the name of a deleted branch for a new branch.
If you use your own Git repository, deleting a branch in the Data Productivity Cloud does not delete the remote version of the branch. To permanently delete a branch, you also need to delete the remote version via your Git provider. To reuse the name of a deleted branch, you need to delete both versions of the branch.
Note
You can sort the Branches menu by name or by default environment.
Branch protection
Enforcing branch protection rules is highly recommended, especially for your main branch or your default branch. This ensures that only approved changes are pushed or merged into your production branch. The Data Productivity Cloud's integration with supported Git providers uses OAuth 2.0. This means that any branch protection rules or permissions that apply to a user will be honored in the Data Productivity Cloud.
To set up branch protection rules in your Git provider, read the documentation below: