Cloning a non publishing repo
Sean Farley
sean at farley.io
Tue Apr 25 20:42:56 UTC 2017
Gregory Szorc <gregory.szorc at gmail.com> writes:
> If I recall, there are some good reasons we do things the way they are. Something about preventing accidental changes? Possibly shared server workflows?
>
> That being said, I've been burned by local clones promoting draft changesets to public. I really wish local clones (or pushes and pulls) didn't do that by default because it is super annoying when working with local clones.
I set:
[phases]
publish = False
in my ~/.hgrc years ago and haven't looked back. I guess the argument is
having less config options is a Good Thing.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 800 bytes
Desc: not available
URL: <http://lists.mercurial-scm.org/pipermail/mercurial/attachments/20170425/b795360d/attachment.asc>
More information about the Mercurial
mailing list