Prepare frontend for handling managing protected branches custom ability
What does this MR do and why?
This is preparation for handling managing protected branches custom ability.
The reason for creating this MR is to keep scope of merge requests smaller.
There are no changes in the application behavior.
MR acceptance checklist
Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.
Screenshots or screen recordings
Screenshots are required for UI changes, and strongly recommended for all other merge requests.
Before | After |
---|---|
How to set up and validate locally
Go to project - settings - repository and play with protected branches section.
Related to #448823 (closed)