Re: [PATCH] tag: add tag.gpgSign config option to force all tags be GPG-signed

From: Mkrtchyan, Tigran <tigran.mkrtchyan@desy.de>
Date: Oct 26, 2017, 21:01 UTC
Message-ID: <1113033991.3307260.1509051676201.JavaMail.zimbra@desy.de>
In-Reply-To: <20171026205509.2ydjd3bai2l6pqxi@aiede.mtv.corp.google.com>

Well, this is a build/release process where we can't pass additional command line options to git. TO be hones, is case of annotated tags there is already option tag.forceSignAnnotated. However, non annotated tags are not forced to be signed.

Additionally, the proposed option is symmetric with commit.gpgSign.

Tigran.

----- Original Message -----

Show 5 quoted lines

> From: "Jonathan Nieder" <jrnieder@gmail.com>
> To: "Tigran Mkrtchyan" <tigran.mkrtchyan@desy.de>
> Cc: git@vger.kernel.org
> Sent: Thursday, October 26, 2017 10:55:09 PM
> Subject: Re: [PATCH] tag: add tag.gpgSign config option to force all tags be GPG-signed

Show 12 quoted lines

> Hi,
> 
> Tigran Mkrtchyan wrote:
> 
>> In some workflows we have no control on how git command is executed,
>> however a signed tags are required.
> 
> Don't leave me hanging: this leaves me super curious.  Can you tell me
> more about these workflows?
> 
> Thanks and hope that helps,
> Jonathan