When deployment pull requests are enabled, Tulip enforces the status of the linked pull request, preventing deployments unless the pull request is mergeable in Git. To ensure this process aligns with your requirements, it is strongly recommended to establish appropriate branch protection rules for your application connection branches. These rules might include:
Requiring approval from n reviewers before deployment.
Automatically revoking approvals if changes are made to the pull request.
Running automated tests or other validations as part of the pipeline. Learn more
Which Branches Require Protection?
The branches that need protection in Git are the long-lived branches linked to your application connections during the Git integration process.
The branch name for each application connection appears in the version control section of the application connection's settings page in Tulip.
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.