partial publish on push

[Mitchell Elutovich]

As discussed (on the mercurial-evolve-testers list), to turn off the auto
publishing of changesets that are pushed, the target repo needs to be
defined with phases.publish=false.

We only partially want that behavior.

I have a coworker that is more involved in the devops, and does not want to
learn, change his habits; while he would be happy if we could have the
development branch stay draft and have its history editable (using evolve,
as I've personally been enjoying) and he feels this would be beneficial as
my development work would get pushed to our server and be better backed
up.  Simply speaking, he does not want to learn about phases meaning he
wants it to just happen automatically.  We have a production branch that we
do want to be published when pushed (automatically).  He does feel that if
we should be investing time it might be better used learning git and
gaining access to the additional git toolings.

On the evolve list it was discussed that we'd probably need a python or
server-side extension and it was suggested as this is not strictly related
to evolve to ask here as perhaps someone has already done this and would be
able to share insights.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mercurial-scm.org/pipermail/mercurial/attachments/20230812/d39aad84/attachment.html>