moving non publishing changesets between secret and draft phases and back to secret
Mitchell Elutovich
melutovich at gmail.com
Wed Aug 9 08:39:00 UTC 2023
However for my co-worker, I'm not sure he would let the addition of
auto-publish=abort (or he would perhaps just always use --publish and
defeat the purpose); for his dev repo if I push the changesets (secret ->
draft -> push -> secret ), is there something wrong with switching them
into secret in his dev repo (post the push from my dev repo) (perhaps also
back to secret in mine as well)?
On Fri, Aug 4, 2023 at 1:29 AM Mitchell Elutovich <melutovich at gmail.com>
wrote:
>
>
> ---------- Forwarded message ---------
> From: Mitchell Elutovich <melutovich at gmail.com>
> Date: Fri, Aug 4, 2023 at 12:58 AM
> Subject: Re: moving non publishing changesets between secret and draft
> phases and back to secret
> To: Pierre-Yves David <pierre-yves.david at ens-lyon.org>
>
>
> I think that would work for me to add
> experimental.auto-publish=abort
> and when pushing to use push --publish
> When would one want to still use secret phase when using this
> auto-publish=abort setting?
>
> However for my co-worker, I'm not sure he would let the addition of
> auto-publish=abort (or he would perhaps just always use --publish and
> defeat the purpose); for his dev repo if I push the changesets (secret ->
> draft -> push -> secret ), is there something wrong with switching them
> into secret in his dev repo (post the push from my dev repo)?
>
> On Fri, Aug 4, 2023 at 12:08 AM Pierre-Yves David <
> pierre-yves.david at ens-lyon.org> wrote:
>
>> Looks like you want to set your mercurial to abort on implicit publish
>> (i.e. push without --public). You have to set the following config :
>> experimental.auto-publish=abort
>>
>> On 8/3/23 21:53, Mitchell Elutovich wrote:
>> > 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-testers at lists.mercurial-scm.org
>> >
>> https://lists.mercurial-scm.org/mailman/listinfo/mercurial-evolve-testers
>>
>> --
>> Pierre-Yves David
>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mercurial-scm.org/pipermail/mercurial-evolve-testers/attachments/20230809/117ed5c5/attachment.html>
More information about the Evolve-testers
mailing list