My co-worker and I have decided not to have a separate non-publishing development repo.
I would like to suggest to him we at least have our personal development repos as non publishing. We have a branch I'll call prod which has one head tagged that is the actual head used in production. There are times that this prod branch has other public heads of work ready to be merged into the actual prod head. (Eventually we might be able to reduce/stop that (having forced pushed heads)) I currently have a topic based on one of those ready public heads (already on the prod repo on the server), if I push (to the prod repo on our server) the topic, mercurial will allow it as it is not creating a new head and then the changesets will become public. So I currently have those changesets as secret to prevent accidental pushing of them. If my co-workers' dev repo is non publishing, I can change them to draft and push them and I understand the topic will stay (assuming he has the topic extension); is there something wrong if we for both his and my dev repo's change the topic revs [back] to secret so that they are not erroneously pushed before we are ready?
_______________________________________________ Evolve-testers mailing list evolve-test...@lists.mercurial-scm.org https://lists.mercurial-scm.org/mailman/listinfo/mercurial-evolve-testers
