Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Closed
worthy7 opened this issue Oct 7, 2019 · 3 comments
Closed

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

worthy7 opened this issue Oct 7, 2019 · 3 comments
Labels
issue/confirmed Issue has been reviewed and confirmed to be present or accepted to be implemented type/proposal The new feature has not been accepted yet but needs to be discussed first.

Comments

@worthy7
Copy link

worthy7 commented Oct 7, 2019

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!

@bagasme
Copy link
Contributor

bagasme commented Oct 7, 2019

Please consider also the case when the approvers are writers, as per #8288 (which I open the issue).

@stale
Copy link

stale bot commented Dec 6, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

@stale stale bot added the issue/stale label Dec 6, 2019
@lunny lunny added the type/proposal The new feature has not been accepted yet but needs to be discussed first. label Dec 6, 2019
@stale stale bot removed the issue/stale label Dec 6, 2019
@lunny lunny added issue/confirmed Issue has been reviewed and confirmed to be present or accepted to be implemented issue/stale labels Dec 6, 2019
@stale stale bot removed the issue/stale label Dec 6, 2019
@kdumontnu
Copy link
Contributor

kdumontnu commented Aug 22, 2024

I think this issue is pretty out of date and should be closed.

There are still some things that need to be explained better in the UI (see discussion here). Specifically:

Here is what the page currently looks like:

image

@lunny lunny closed this as completed Aug 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
issue/confirmed Issue has been reviewed and confirmed to be present or accepted to be implemented type/proposal The new feature has not been accepted yet but needs to be discussed first.
Projects
None yet
Development

No branches or pull requests

4 participants