Using Mercurial Shelve to Temporarily Set Aside Uncommitted Changes
Learn how to store local edits with hg shelve, work on another task, and restore the changes safely.
ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Learn how to store local edits with hg shelve, work on another task, and restore the changes safely.
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.
Learn how to shelve an instance to shared storage, free its compute host, and later unshelve it safely, with verification steps and known limitations.
The shelve command stores changes as a bundle in .hg/shelve . When the working directory contains large binary files, those binaries are included unchanged in the bundle, which can cause the shelve directory to grow unexpectedly and affect disk usage in CI pipelines that rely on shelve for temporary storage. The documentation does not specify whether shelve