We've talked about our new plan for epic branches. OK, I'll start.

Here's what I intend to do:

• Open a new epic branch, with an opening commit (the opener).
• Open a Pull Request from this branch against master.
• Add a checklist in the description, describing (albeit not necessarily committing) to the conditions which will warrant merge.

Rules I think make sense:

• I'll make up a silly title for myself (I'm going with "chaperone"), and I'll put, in the description, "chaperones". Other people may add themselves. Doing so is a commitment to do the following things:
  ** Conduct rebases over master.
  ** Conduct merges into the epic branch.
  ** Work with any contemporaneous epickers to manage which PRs are in and which are out.
• All merge commits within this epic must include the opener - in other words, no merge commits are allowed between sub-PRs; only from sub-PRs to the epic. All other commits must be rebased such that this commit is in the history, with a lineal sequence maintained by the author until merge.
• All reviews for PRs going in are subject to some kind of checklist or templating. It is apparently not possible to auto-populate the review field on github as it is with the PR description field. See: https://github.community/t5/How-to-use-Git-and-GitHub/Pull-Request-Review-Template/td-p/6857