Making "hg push -r foo" changes phases

[Laurens Holst]

I think there's no need to continue discussing removing --force for 
moving from draft to secret.

As I said previously there's no need to force if you create the commit 
as secret straight away, and the desire to do something that needs to be 
forced is a symptom of a different problem; that you didn't create the 
commit as secret in the first place.

The correct way to do this is thusly:

     hg commit --config new-commit=secret

Doing it this way is by design[1], quote:

On Mon, 2011-12-19 at 14:36 +0100, Matt Mackall wrote:
> On Mon, 2011-12-19 at 11:46 +0100,pierre-yves.david at logilab.fr  <http://selenic.com/mailman/listinfo/mercurial-devel>  wrote:
>> /The only way to create a secret changeset for now is to add a --secret switch to
>> //commit. [...]///
> I think this is a little too invasive.
>
> Another alternative is to have a default phase in the config. This will
> allow code that wants to temporarily override the mode to do it by
> tweaking ui. It'll also allow knowledgeable users to make things work
> for them for random commands with --config phases.default=secret.
> We do something similar with merge tools and ssh options.
>
> But I think we want to make phases generally work without users needing
> to think about them. So for instance, we should have MQ make changesets
> secret by default.

Let's focus the discussion on how to make that easier. I propose a 
--secret flag on commit.

~Laurens

[1] http://selenic.com/pipermail/mercurial-devel/2011-December/036474.html
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://selenic.com/pipermail/mercurial-devel/attachments/20130618/e0799384/attachment.html>