If your Salto organization was created before November 26, 2024, the branches requiring protection might not be the environment branches themselves. Instead, Salto will display branch name patterns in the UI to guide your protection setup. These patterns include:
A specific pattern for the environment you’re viewing.
A global pattern that applies to all Salto environments configured to use pull requests for deployments.
If you’d like to upgrade your Salto organization to support the new branch strategy, please contact our support team for assistance.
Refer to the image below for an example of branch name patterns displayed in the Salto UI.
Step-by-Step Instructions for Configuring Branch and Merge Protection per Git Provider
Each Git provider manages branch and merge protection settings differently. To ensure your configurations are correct, follow the specific instructions for the Git solution connected to your system:
GitHub: Learn how to set up branch and merge protection rules in GitHub Cloud.
GitLab: Detailed steps for configuring protection rules in GitLab.
Bitbucket: Instructions for setting up branch and merge protection in Bitbucket.
Azure DevOps: Guide to applying branch protection rules in Azure DevOps.