Skip to content

Make Protected Branches -> Approvals section easier to understand #8407

Closed
@worthy7

Description

@worthy7

Small issue concerning UX design which at least caused me a little bit of confusion.

  1. Allow only to merge pull request with enough positive reviews of whitelisted users or teams.
    -> Allow merging of pull requests only with enough positive reviews from approvers.

  2. Whitelisted reviewers: -> Reviewers:

  3. default text set to Search contributing teams or users...

  4. Add a checkbox first saying "Require approvals", when unchecked the two options are disabled, when checked, the "number of approvals" is minimum 1 and the input for Approvers should be "required" (input required). Doing a dynamic calculation to see if they match is not worth it since team sizes can change in the future

For reference here is how GitHub looks
image

I made a mock-up design for someone to follow:
image

Open for discussion!

Metadata

Metadata

Assignees

No one assigned

    Labels

    issue/confirmedIssue has been reviewed and confirmed to be present or accepted to be implementedtype/proposalThe new feature has not been accepted yet but needs to be discussed first.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions