Version Control Settings Block for React

Edit SAVED: each branch has an id, a label, whether it is protected, the approvals it needs, the three switches and the merge methods it allows. METHODS lists the methods and COUNTS the approval choices. The sentence on top, the verdict and the unsaved count are all worked out from those, so a new branch or method shows up in every part.

It is a pure function of the branch's rule and the pull request, and nothing merges. A protected branch lists every reason a pull request is blocked: too few approvals (counted as none when stale approvals are dismissed and new commits came after them), checks that haven't passed, unsigned commits and a merge method the rule doesn't allow. The first reason is the headline and all of them are listed under it; with none left it says it can merge by the method wanted. An unprotected branch says anyone can merge.

It lets anyone with write access merge whatever the approvals and checks say, so it asks in an alert dialog that opens with focus on Keep protection and can't be dismissed by clicking outside it. The rules are kept and dimmed while protection is off, and turning it back on needs no question. Focus returns to the switch when the dialog closes.

Everything. Save keeps the rules in this page's state and a reload brings back the starting ones; the tester asks no server. To make it real, store the rules per branch pattern on your server, enforce them where merges happen (the host's branch protection API or your own merge queue), and use the same function to preview a pull request's status from its real approvals, checks and signatures.

A protected branch with no merge method allowed, because nothing could merge into it. Save names the branch, switches to it, marks the methods and moves focus to the first checkbox. The sentence on top says the same thing as soon as the last method is unticked: no merge method is allowed, so nothing can merge.

The rules come first and the tester under them, each control with a visible label and a hint, the three toggles in a column and the verdict in a card whose list reserves room for every reason, so the page doesn't move when the answer changes. The branch picker and the segment groups are real groups with labels, the box and the name of each merge method are one hit area, and a new verdict is read out once you stop changing the pull request, not on every press.