Should Mercurial add a stash-or-merge option to hg pull -u for repeatable environments?
Context In Mercurial 6.x the command hg pull -u aborts when incoming changesets would overwrite uncommitted modifications in the working directory. This behavior guarantees that a repeatable development environment stays unchanged after a failed pull, but it forces developers to manually commit, shelve, or discard local edits before updating. Unresolved deci