Do you have or know of writeups describing this workflow in more detail? I'm interested in learning more.
This workflow is described in the documentation for the mercurial evolve extension: https://www.mercurial-scm.org/doc/evolution/
Re:Mercurial 4.0 Sprint Notes
by marcinkuzminski on Wednesday October 19, 2016 @07:50AM
(#12742936)
Here's a blog post on how to use Bookmarks in Mercurial workflow using code-review.
We back ported from one of the guys that works for us and described our workflow:
https://rhodecode.com/blog/120/mercurial-workflow-using-book...
If you use phases (draft/secret/public) correctly it's really close to being mutable. For example all our devs forks are having non-publishing repositories since it's a private non-shared space. By keeping all commits as draft it's easy to do a rebase and then push new changed commits.
While the main repo is publishing and once pushed commits are never mutable, also we keep a workflow that only dev forks can have multiple heads while production repo cant.
IMHO it's the nicer form of mutability