How to enforce remote gnupg signing of Mercurial repository only when new tags are created?

Posted by Tim Post on Stack Overflow See other posts from Stack Overflow or by Tim Post
Published on 2010-04-10T02:09:26Z Indexed on 2010/04/10 2:13 UTC
Read the original article Hit count: 340

Filed under:
|

I know how to configure the Mercurial signing extension. The problem that I'm having is that I don't want to sign each individual change set, I only want to sign revisions that introduce new version tags.

That's easily accomplished locally, however I can't come up with a way to enforce this on the remote server. I'd like people to continue to be able to push their changes as normal, unless adding a release tag, which should be accompanied by a signature.

The end result should be that anyone cloning our repository can easily see a list of signed revisions, which point to a list of signed releases.

Hopefully, I've just missed something obvious in hooklib. Has anyone else accomplished this, if so, how?

© Stack Overflow or respective owner

Related posts about mercurial

Related posts about version-control