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

hook for rebase --continue

From
Matt Graham <mdg149@gmail.com>
Date
Nov 7, 2011, 19:42 UTC
Message-ID
<CALts4TQ545L1d1J0EiUjd7x=WBJpjCCv6UsXZOoGQAC29RqC5g@mail.gmail.com>

Hi, I did some testing and it appears that during a rebase, if I resolve a conflict and call git rebase --continue, the pre-commit hook doesn't run. This means that if I don't resolve the conflict correctly, our check for invalid syntax doesn't get run and creates the risk that someone could push code with invalid syntax, not realizing that the check didn't run.

Does anyone else share my expectation that the pre-commit hook should run during a rebase? Or at least for the first commit following a rebase conflict?

If not, is there another hook that is triggered by a rebase that I should be using instead?

Thanks, Matt

Next: Martin Fick
Message 1 of 5 in “hook for rebase --continue”
  1. Matt GrahamNov 7, 2011
  2. Martin FickNov 7, 2011
  3. Neal KreitzingerNov 10, 2011
  4. Neal KreitzingerNov 10, 2011
  5. Neal KreitzingerNov 15, 2011

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.