Thanks for the hg facilities!

[Arne Babenhauserheide]

Am Montag, 5. Januar 2015, 09:25:10 schrieb Harry .:
> The workflow where I've seen this problem a lot is:
> 
> - Tag release x
> - Wait for a cooling-off period before pushing to publishing repository
> - In the meantime, start work on x+1
> - After the cooling off period, push -r x
> - Result: Publishing repository doesn't have tag x

That sounds like a nasty one, yes.

To ensure that the target repo has the tag, you can check at which
revision the tag was created (though this is a bit of a hack - it
might be useful to clean this up as an extension):

    [alias]
    publish = !hg push -r $(hg annotate .hgtags | grep $1 | cut -d : -f 1)

This requires the discipline to always tag the current revision,
though (never to hg tag -r X <name>, only the plain tag <name>).

You could also extend it quite easily to also include the GPG signing
revision (created using the gpg extension).

Best wishes,
Arne
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 299 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.mercurial-scm.org/pipermail/mercurial/attachments/20150106/5eb56f6d/attachment.asc>