moving non publishing changesets between secret and draft phases and back to secret
Mitchell Elutovich
melutovich at gmail.com
Thu Aug 3 19:53:11 UTC 2023
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?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mercurial-scm.org/pipermail/mercurial-evolve-testers/attachments/20230803/d85baee8/attachment.html>
More information about the Evolve-testers
mailing list