10.08.2023 16:05, Mitchell Elutovich пишет:
Just to highlight for this scenario, even though we've already
discussed, when the draft changeset is "pushed", the *target *repo that
is being pushed into will need to have off the auto publishing of draft
changesets.
[phases]
publish = false
Right, this will have an effect of drafts pushed to such a repo staying
drafts. If you also push/pull work-in-progress to/from colleagues
directly, then it's advisable to have publish=false set for those repos
as well.
And I'd say if you all work with topics and evolve, having publish=false
in your user-global ~/.hgrc is also recommended. After all, you can
publish commits more easily than turn them back into drafts.
This would only likely work if the colleague would himself agree to have
a limited main:pushrev
Technically there's also an option to prevent pushing certain changesets
to the main repo via a hook, this could be a way of preventing
accidental pushes. For example, only allow already public changesets
into the main dev repo: this way you'll have to review and publish work
locally, and exchange work-in-progress via direct exchange with your
colleagues. (Then publish=false wouldn't make much sense in the main dev
repo). I haven't tried this workflow, not sure how comfortable it is.
_______________________________________________
Evolve-testers mailing list
evolve-test...@lists.mercurial-scm.org
https://lists.mercurial-scm.org/mailman/listinfo/mercurial-evolve-testers
