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

Re: Please add support for "git merge --continue -S"

From
Ævar Arnfjörð Bjarmason <avarab@gmail.com>
Date
Feb 28, 2022, 10:58 UTC
Message-ID
<220228.86fso35k61.gmgdl@evledraar.gmail.com>
In-Reply-To
<3769291.LUJhsIL6D6@mobilepool36.emlix.com>
On Mon, Feb 28 2022, Rolf Eike Beer wrote:
Show 14 quoted lines
> [[PGP Signed Part:Undecided]]
> Hi,
>
> I usually sign my commits and merges. But when a merge has collisions I can't 
> continue and sign in one step, because --continue and -S seem to be mutually 
> exclusive. My way out is:
>
> git merge --continue
> git commit --amend --no-edit -S
>
> ... but this could be a bit simpler. Or maybe --continue could remember if I 
> have passed "-S" to the original "git merge" command.
>
> Regards,

You can just drop the use of "merge --continue" entirely and use "commit" instead.

Caveats related to this were recently discussed on-list: https://lore.kernel.org/git/CALRdAfcyfesNqfLhhe2GW_5V9s2hf++i6mZS1Lw5hqQYTca85w@mail.gmail.com/

As noted there I think this makes for confusing UI, but you should able to just:
    git commit -S
Previous: Rolf Eike BeerNext: Junio C Hamano
Message 2 of 4 in “Please add support for "git merge --continue -S"”
  1. Rolf Eike BeerFeb 28, 2022
  2. Ævar Arnfjörð BjarmasonFeb 28, 2022
  3. Junio C HamanoFeb 28, 2022
  4. Ævar Arnfjörð BjarmasonFeb 28, 2022

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.