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.
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.
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.
Enrollment-level branch protection
Administrators can enable branch protection by default for all new pipelines within an enrollment. Branch protection enhances the security and integrity of your repository by requiring proposals to be approved before any changes can be made to a protected branch.
Enabling enrollment-level branch protection will not affect existing pipelines. To change the branch protection of existing pipelines, see how to protect branches above.
Go to Control Panel and navigate to Pipeline Builder. Then, toggle the setting for Enable branch protection by default for new pipelines. This will force all protected branches on new pipelines to require a proposal before changes can be merged.