ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Developer tools · #mercurial
Mercurial's rebase extension turns a tangled feature branch into a clean linear history for easier review. Learn when to use it, how to enable it, and a step-by-step example rebasing a local branch onto an updated default—while respecting phases safety.
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.
hg share lets multiple Mercurial working directories read one .hg store. This architecture note covers the trust boundary, safe usage rules, failure modes, and when full clones are the better design.
Learn how to use Mercurial’s phases (draft, secret, public) to prevent accidental pushes of unfinished work and choose the right state for each changeset in a collaborative workflow.
Mercurial push failures and "can't rebase public changesets" errors usually trace back to the phase system. Learn to diagnose draft, secret, and public states and fix them safely.
Mercurial's phase system (draft, secret, public) controls which operations are allowed on changesets, preventing accidental history corruption in shared repositories.
Learn how Mercurial Named Branches provide permanent metadata for project lineage, contrasting them with bookmarks to avoid the problem of anonymous heads.
Learn how Mercurial’s phase system lets you commit unfinished work locally, promote it when ready, and avoid accidental exposure while keeping history clean.
Learn how to use Mercurial’s shelve extension to stash uncommitted changes, switch context, and share patches without committing. A step‑by‑step guide, trade‑offs, and a practical example are included.