No --no-gpg-sign option with "git rebase"

Luca Weiss· Oct 18, 2018, 16:01 UTC · lore

See subject, would be quite useful to have this. ("Countermand commit.gpgSign configuration variable that is set to force each and every commit to be signed.")

Thanks, Luca

Johannes Schindelin· Oct 19, 2018, 15:30 UTC · re: Luca Weiss · lore

Re: No --no-gpg-sign option with "git rebase"

Hi Luca,

On Thu, 18 Oct 2018, Luca Weiss wrote:

> See subject, would be quite useful to have this. ("Countermand commit.gpgSign 
> configuration variable that is set to force each and every commit to be 
> signed.")

Have you tried the built-in rebase? It's already available in `next`, and it is available in Git for Windows as an experimental feature.

Ciao, Johannes

Johannes Schindelin· Oct 22, 2018, 09:01 UTC · lore

Re: No --no-gpg-sign option with "git rebase"

Hi Luca,

I re-Cc:ed the Git mailing list (it is in general a very good idea to keep it in Cc:, as I could be hit by a bus, for example).

On Fri, 19 Oct 2018, Luca Weiss wrote:

Show 13 quoted lines

> On Freitag, 19. Oktober 2018 17:30:17 CEST you wrote:
> 
> > On Thu, 18 Oct 2018, Luca Weiss wrote:
> > > See subject, would be quite useful to have this. ("Countermand
> > > commit.gpgSign configuration variable that is set to force each and
> > > every commit to be signed.")
> > 
> > Have you tried the built-in rebase? It's already available in `next`,
> > and it is available in Git for Windows as an experimental feature.
>
> in the 'next' branch the option "--no-gpg-sign" is actually accepted for
> git rebase (not listed in "--help" output or the man page though) but
> git still tries to sign each commit.

Did you get a chance to debug this?

Ciao, Johannes