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

rebase has no --verify-signatures

From
Alexander 'z33ky' Hirsch <1zeeky@gmail.com>
Date
Dec 7, 2015, 14:00 UTC
Message-ID
<20151207140015.GA14956@netblarch.tu-darmstadt.de>
Hi,
The git merge command has a --verify-signatures flag, which, when set, checks that the commits to be merged have trusted GPG signatures. git pull also knows this flag and forwards it to the merge command.
However, doing a git pull --rebase --verify-signatures silently ignores it, since rebase has no --verify-signatures flag.
Is there any technical reason why rebase should not have a --verify-signatures flag? I have written a patch to git-rebase--am which enables it to do such a check. If there is no reason not to include it I'd add documentation and a test and submit it.
Otherwise I think git pull should warn, or even die with an error, if both --rebase and --verify-signatures are passed.

Regards, Alexander Hirsch

Next: brian m. carlson
Message 1 of 3 in “rebase has no --verify-signatures”
  1. Alexander 'z33ky' HirschDec 7, 2015
  2. brian m. carlsonDec 8, 2015
  3. Alexander 'z33ky' HirschDec 9, 2015

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.