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

Re: git rebase interactive breaks when working on a secondary worktree

From
Denilson Sá Maia <denilsonsa@gmail.com>
Date
Jun 26, 2025, 18:33 UTC
Message-ID
<CACGt9ymuLOaA7dK-Y-g0WR99EKgknsuXzOpEd8xqpNOpcK_38A@mail.gmail.com>
In-Reply-To
<bec18631-c0c5-4e8d-99ca-7f2bbdd5e88f@app.fastmail.com>

On Thu, 26 Jun 2025 at 17:58, Kristoffer Haugsbakk <kristofferhaugsbakk@fastmail.com> wrote:

Show 20 quoted lines
>
> On Thu, Jun 26, 2025, at 12:49, Denilson Sá Maia wrote:
> >
> > [Enabled Hooks]
> > applypatch-msg
> > commit-msg
> > post-applypatch
> > post-checkout
> > post-commit
> > post-merge
> > post-rewrite
> > pre-applypatch
> > pre-auto-gc
> > pre-commit
> > pre-merge-commit
> > pre-push
> > pre-rebase
> > prepare-commit-msg
>
> A lot of hooks. Do you use git-branchless?

We are using Husky in our corporate/enterprise/business application. And I think husky hooks itself into all git hooks, and that's why I have so many of them. https://github.com/typicode/husky

But inside our `.husky/` directory inside our git repository we only have `commit-msg` and `pre-push` hooks configured. Everything else is unused. (Which probably means Husky gets called, but does absolutely nothing.)

-- 
Denilson Figueiredo de Sá Maia
https://denilson.sa.nom.br/
Previous: Kristoffer HaugsbakkNext: Phillip Wood
Message 3 of 5 in “git rebase interactive breaks when working on a secondary worktree”
  1. Denilson Sá MaiaJun 26, 2025
  2. Kristoffer HaugsbakkJun 26, 2025
  3. Denilson Sá MaiaJun 26, 2025
  4. Phillip WoodJun 27, 2025
  5. Denilson Sá MaiaJun 27, 2025

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.