push to remote, feature branch at tip, but not when cloned

[Uwe Brauer]

   > On 12/18/19 9:18 PM, Uwe Brauer wrote:

   > I guess my question are: Why do you need a new branch for? and Why do
   > you want it to be the default checkout?

Well I push the repository to two different remote servers

    1. Bitbucket and then the notify extension notifies user1

    2. Helix and then the notify extension notifies user2

I have not found a way to configure the notify extension in such a way
that it would differentiate whom to notify depending on where I want to
push. The all_path extension allows me to push at once to all the remote
sites, but, again, does not allow to differentiate the notify extension.


So that is why I use default branch for user2 and the feature branch for
user1.

The issue is that both users don't want to be bothered with too many hg
commands.

If you cold tell me how to configure notify in such a situation I would
be very grateful. I could not figure it out myself, nor google.

Regards

Uwe 



-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5025 bytes
Desc: not available
URL: <http://lists.mercurial-scm.org/pipermail/mercurial/attachments/20191219/96f94b3c/attachment.p7s>