### Description As part of the [MVC](https://gitlab.com/gitlab-org/gitlab/-/issues/351468) for organizing rules based on branches, we need to implement the ability to add branch protections. ### Scope The scope of this issue includes: * ~~Implement branch/wildcard dropdown~~ * Handled by https://gitlab.com/gitlab-org/gitlab/-/issues/388128 * Implement the Access level dropdowns * Implement Push access checkbox * Implement 'realtime' saving (use existing endpoint) ### Implementation plan <details> <summary>Details</summary> | issue | note | | ------ | ------ | | https://gitlab.com/gitlab-org/gitlab/-/issues/362205+ | | | https://gitlab.com/gitlab-org/gitlab/-/issues/362212+ | :point_left: **this issue** | | https://gitlab.com/gitlab-org/gitlab/-/issues/362214+ | | | https://gitlab.com/gitlab-org/gitlab/-/issues/362219+ | | | https://gitlab.com/gitlab-org/gitlab/-/issues/362217+ | :warning: blocked by https://gitlab.com/gitlab-org/gitlab/-/issues/362219 | | https://gitlab.com/gitlab-org/gitlab/-/issues/362218+ | :warning: blocked by https://gitlab.com/gitlab-org/gitlab/-/issues/362219 | Update `editBranchRule` mutation to include these fields </details> ### Mockups <details> <summary>Details</summary> [Figma](https://www.figma.com/file/eq2nf3B8MhB9xKrC0VzbPf/Repository?type=design&node-id=916%3A5174&mode=design&t=zrP2cLygKOMQqcde-1) </details> #### Allowed to merge - Allows editing of roles, users, and groups - Default: - Roles: Administrators, Maintainers - Empty state text: No one is allowed to merge changes. - On change, display toast "Allowed to merge updated" - Undo action would be nice to have. <details> <summary>Details</summary> | Default | Edit - default | Edit - filled | Allowed to merge updated | ------ | ------ | ------ | ------ | | |  |  |  | </details> #### Allowed to push and merge - Allows editing of roles, users, groups, and deploy keys - Default: (empty) - Empty state text: Everyone is required to submit a merge request for changes. - On change, display toast "Allowed to push and merge updated" - Undo action would be nice to have. <details> <summary>Details</summary> | Default | Edit - filled | Allowed to push and merge updated | | ------ | ------ | ------ | |  |  |  | </details> #### Toggles - `Allow force push` toggle is only displayed when there "allowed to push and merge" is populated - Default off - `Requires code owner approval` - Default off - Toast displayed when toggle changes <details> <summary>Details</summary> | Allow force push enabled | Require code owners approval enabled | | ------ | ------ | |  |  | </details> #### Everyone is required to submit a merge request for changes <details> <summary>Details</summary> It is not obvious that you need to set roles to "No one" in protected branches to enforce the fact that everyone is required to submit a merge request for changes. Here is our guidance in [our docs](https://docs.gitlab.com/ee/user/project/protected_branches.html#require-everyone-to-submit-merge-requests-for-a-protected-branch). This is compounded by the fact that you could select a role as "No one" but still include users and groups - selecting the role of "No one" is redundant in this scenario. To help with convey this scenario to make it clear for users who want to enforce merge requests for branches like these related issues https://gitlab.com/gitlab-org/gitlab/-/issues/384939+ and https://gitlab.com/gitlab-org/gitlab/-/issues/388102+ | Introducing toggle to require merge request | Toggled true | "Everyone is required to submit a merge request" | | ------ | ------ | ------ | |  |  |  | </details>