3 ms·
CTO of RhodeCode here. If you use phases (draft/secret/public) correctly it's really close to being mutable. For example all our devs forks are having non-publ
by marcinkuzminski 10y ago
CTO of RhodeCode here.
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
- Bjartr 10y agoDo you have or know of writeups describing this workflow in more detail? I'm interested in learning more.
- ngoldbaum 10y agoThis workflow is described in the documentation for the mercurial evolve extension: https://www.mercurial-scm.org/doc/evolution/ https://www.mercurial-scm.org/doc/evolution/
- marcinkuzminski 10y agoHere'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-bookmarks-how-to-setup-and-use https://rhodecode.com/blog/120/mercurial-workflow-using-book...