Design 47 H2, lead answer H-A-471 and its two addenda (hq branch design/47-H1-answers-59: 8fd62a24 "the note and merge-called", cb1b7176 "plain merges need a read view").
What changed
The seat git's contract (mesh-delivery-contracts): a merge call's member outcome (MemberOutcome, CallMember) gains an optional note, "no delivery: the repository has no watched branch", for a member whose repository has no watched branch; it is merged plainly and merge-called leaves it out, so it starts no delivery. The seat's form rises to 3; merge-pull's description says it. Go and TypeScript bindings, seat.json and fixtures updated.
Tests run
seatgen -check: clean
contract fixtures (states.json, verbs.json) and contract_test.go pass
Reviewed-by: mesh-code-reviewer@shanks at 3f72078853
Pushed-by: lead-47@shanks
## Design lines
Design 47 H2, lead answer H-A-471 and its two addenda (hq branch design/47-H1-answers-59: 8fd62a24 "the note and merge-called", cb1b7176 "plain merges need a read view").
## What changed
The seat git's contract (mesh-delivery-contracts): a merge call's member outcome (MemberOutcome, CallMember) gains an optional note, "no delivery: the repository has no watched branch", for a member whose repository has no watched branch; it is merged plainly and merge-called leaves it out, so it starts no delivery. The seat's form rises to 3; merge-pull's description says it. Go and TypeScript bindings, seat.json and fixtures updated.
## Tests run
- seatgen -check: clean
- contract fixtures (states.json, verbs.json) and contract_test.go pass
Reviewed-by: mesh-code-reviewer@shanks at 3f720788538b8c5edcb519b8b9e714291e73b3f0
Pushed-by: lead-47@shanks
Group: mesh-delivery #326 + mesh-catalog #736 (one merge call)
A repository with no watched branch is the forge's business alone: the
seat git's merge-pull merges such a member plainly and starts no delivery.
MemberOutcome and CallMember gain an optional note saying so ("no delivery:
the repository has no watched branch"), why staying the refusal's; the
kept field is what merge-called leaves the member out by. The seat's form
rises to 3; merge-pull's description says it.
Builds: design 47 H2 H-A-471 and its addendum (1)
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Design lines
Design 47 H2, lead answer H-A-471 and its two addenda (hq branch design/47-H1-answers-59: 8fd62a24 "the note and merge-called", cb1b7176 "plain merges need a read view").
What changed
The seat git's contract (mesh-delivery-contracts): a merge call's member outcome (MemberOutcome, CallMember) gains an optional note, "no delivery: the repository has no watched branch", for a member whose repository has no watched branch; it is merged plainly and merge-called leaves it out, so it starts no delivery. The seat's form rises to 3; merge-pull's description says it. Go and TypeScript bindings, seat.json and fixtures updated.
Tests run
Reviewed-by: mesh-code-reviewer@shanks at
3f72078853Pushed-by: lead-47@shanks
Group: mesh-delivery #326 + mesh-catalog #736 (one merge call)
A repository with no watched branch is the forge's business alone: the seat git's merge-pull merges such a member plainly and starts no delivery. MemberOutcome and CallMember gain an optional note saying so ("no delivery: the repository has no watched branch"), why staying the refusal's; the kept field is what merge-called leaves the member out by. The seat's form rises to 3; merge-pull's description says it. Builds: design 47 H2 H-A-471 and its addendum (1)