Safe Shared History Rewriting in Mercurial with hg-evolve
Use Mercurial's hg-evolve extension and obsolescence markers to amend pushed commits without breaking teammates' checkouts.
Loading…
ReadMeFeed / Community knowledge
#hg-evolve
Real questions. Useful conversations. Find the people who know your stack.
mercurialEvolve extension: Managing obsolescence marker propagation during repository pruning
The evolve extension introduces obsolescence markers to track commit mutations, allowing history rewriting to propagate across clones without necessitating hard resets. While this enables a mutable history, the prune operation permanently removes these obsolete commits from the local store to optimize disk space. A technical uncertainty exists regarding the
Mercurial Evolve Extension and Shared Repository Obsolescence Markers
Integration of Mutable History in Collaborative Workflows The evolve extension introduces obsolescence markers to Mercurial to manage history rewriting across clones. While this allows for a managed mutable history, the interoperability between clients using the extension and those relying on core Mercurial functionality creates a synchronization boundary. W