As discussed, 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 and 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 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.
_______________________________________________ Evolve-testers mailing list evolve-test...@lists.mercurial-scm.org https://lists.mercurial-scm.org/mailman/listinfo/mercurial-evolve-testers
