Rename setting to `block_branch_modification`
Why are we doing this work
Relevant links
Non-functional requirements
-
Documentation: -
Feature flag: -
Performance: -
Testing:
Implementation plan
-
frontend rename block_unprotecting_branches
toblock_branch_modification
-
backend rename block_unprotecting_branches
toblock_branch_modification
Verification steps
- Upload a GitLab Ultimate license
- Navigate to a project => Settings => Repository => Protected Branches
- Protect several branches
- Navigate to Secure => Policies => New policy => Scan Result Policy
- Create a policy with some of the protected branches selected (or some excepted) and the following settings
approval_settings:
block_branch_modification: true
- Save the policy
- Navigate to the project => Settings => Repository => Protected Branches
- Verify the affected branches cannot be unprotected
- Navigate to Settings => Repository => Branch defaults
- Verify if the default branch is included in the policy, that the default branch cannot be changed
- Navigate to Code => Branches
- Verify the affected branches cannot be deleted
Edited by Alexander Turinske