{"thread":{"id":"59609","subject":"What hook is called after `git rebase --abort`?","startedAt":"2023-04-17T11:53:33Z","lastAt":"2023-04-17T11:53:33Z","messageCount":1,"participants":["Konstantin Kharlamov"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"475519","messageId":"0d8c0c2c6f9348a2afea3992f589ab52db5bb434.camel@yandex.ru","threadId":"59609","inReplyTo":null,"subject":"What hook is called after `git rebase --abort`?","fromName":"Konstantin Kharlamov","fromEmail":"hi-angel@yandex.ru","sentAt":"2023-04-17T10:07:25Z","receivedAt":"2023-04-17T11:53:33Z","isPatch":false,"sender":{"key":"hi-angel@yandex.ru","avatar":null},"body":"As title says.\n\nThe usecase is typical: there's the infamous issue of dangling git-submodule changes\nappearing in various operations, leading to problems such as inadvertently commiting\na submodule hash change while editing an irrelevant commit.\n\nI already had sprinkled a few `git submodule update`s in `post-checkout` and\n`post-rewrite` hooks, but I just found one more case: executing a `git rebase\n--abort` to abort a `git rebase` operation that involved changing a submodule commit\nresults in the submodule change appearing in `git diff` even though no rebase\noperation is ongoing. Apparently there's one more hook that requires to have the same\ncommand, any ideas what that could be?\n\nP.S.: please keep me CCed, I'm not subscribed to the list\n\n"}]}