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
#history-rewriting
Real questions. Useful conversations. Find the people who know your stack.
mercurialMercurial Phases: Using Draft, Secret and Public to Guard Your Pushes
Mercurial phases label each changeset as draft, secret or public to prevent accidental publication and support safe history rewriting in team workflows.
Rewriting Local History with Mercurial Rebase
Move local Mercurial changesets onto a new base with hg rebase: prerequisites, conflict handling, phase checks, and how to recover using obsolete revisions.
Mercurial Changeset Evolution: An Architecture Note on Safe History Mutation
How Mercurial's Changeset Evolution uses obsolescence markers and a filtered view to make history rewriting non-destructive, traceable, and safe to share across clones.
GitKraken interactive rebase signature preservation for GPG-signed commits
GitKraken provides a visual interactive rebase interface for reordering, squashing, dropping or editing commits by drag-and-drop in the commit graph. For repositories that use GPG-signed commits, history rewriting invalidates signatures because Git does not automatically re-sign rewritten commits. GitKraken documentation describes GPG signing support for new
gitkraken