mercurial - Is a workflow of hg clone on non-bare hg repositories safe? -
i know git refuse push non-bare repository, hg doesn't seem to... mean not need worry bareness when cloning hg? i've experimented (in pastebin below), , haven't seen problems approach, inability find problems not same there being no problems. also, have autopush enabled in .hgrc...
mercurial not auto-merge when push, pushing non-bare repository safe. why mercurial not distinguish between bare , non-bare repositories - bare repository 1 working directory @ null
revision (i.e. before initial commit).
if pushing new head existing branch mercurial require specify hg push -f
. because having multiple heads on same branch imposes additional complications other developers , potentially result in heads being merged in different ways, leading cascade of unnecessary merges.
the workflow should follow pull; merge new heads existing head; push. of course, depends heavily on branching strategy using - 1 uses bookmarks (equivalent git branches) or anonymous branching tasks end multiple heads on same named branch, whereas 1 using named branches tasks tend not to.
Comments
Post a Comment