Implement proposal lifecycle with conflict, rebase, and idempotent approval #16
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
M1: Users author proposals pinned to a base revision; Curators approve (applies as a change-set, conflict-safe), reject; conflicted proposals rebase or reject; approval idempotent under retry. Acceptance: §11.2.2, §5.3, §9.3, CR-1, CR-17; approver≠author enforced (§4.3, rule exists from #4).