Branch protection

When there are multiple authors contributing to the same Pipeline Builder instance, or when the pipeline backs critical data assets, you can protect your branch to achieve a greater level of governance and defense against unintentional changes. A protected branch can only be modified with a pull request and must satisfy a predefined set of requirements.

How to protect branches

Navigate to the Settings drop down in the top left. Select Manage branches.

Screenshot of the settings dropdown.

Select the Branch protection tab. In this tab, enable Require proposals... to protect the Main branch and any other branches specified in the text box below. Select Save when done.

Screenshot of where to configure multiple protected branches.

All protected branches require users to make changes on a separate branch before those changes can be merged into protected branches. Currently, all protected branches in Pipeline Builder share the same approval rules.