As you start integrating your deployments with pull requests, you should consider which merge protection rules should be applied to support your organizational use cases, e.g.
Ensuring that deployments have been approved by n number of reviewers
Revoke approvals upon deployments changes
Running automated tests, or other automations.
Salto will respect the status of the pull request and deployment will not be allowed if the PR is not mergeable in Git.
Once pull requests are enabled, branch name patterns for protection rules will appear. One pattern corresponds to the specific environment you're viewing, and another applies to all Salto environments configured to have pull requests attached to their deployments.
Step-by-Step Instructions for Specific Git Providers
Each of the supported Git providers handles branch and merge protection in a slightly different manner so follow the instructions for the Git solution connected to your system.