git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: git commit-tree does not honor commit.gpgSign config

From
EGEvan Grim <evangrim@gmail.com>
Date
Sep 28, 2020, 19:42 UTC
Message-ID
<CABX4Un3euDWeGr_2DegS3xyoD8VJ23rb9+bj3hBkWS6KZH9FhA@mail.gmail.com>
In-Reply-To
<xmqqd025n3ik.fsf@gitster.c.googlers.com>

Thank you for that context. I came across this when I used `git-subtree` and was surprised the commits it created weren't signed. Would it be appropriate to look into patching `git-subtree` to honor the configuration option?

On Mon, Sep 28, 2020 at 12:46 PM Junio C Hamano <gitster@pobox.com> wrote:
Show 11 quoted lines
>
> Evan Grim <evangrim@gmail.com> writes:
>
> > Is it a bug that `git-commit-tree` doesn't honor the `commit.gpgSign`
> > configuration option?
>
> It would be a bug if it did, as a low level plumbing tool to build
> scripts around, it would not want its behaviour to be affected by
> end-user configuration (rather, scripts that are written using these
> plumbing command do want to handle end-user customization their own
> ways).
Previous: Junio C HamanoNext: Junio C Hamano
Message 3 of 4 in “git commit-tree does not honor commit.gpgSign config”
  1. Evan GrimSep 28, 2020
  2. Junio C HamanoSep 28, 2020
  3. Evan GrimSep 28, 2020
  4. Junio C HamanoSep 28, 2020

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.