There are a list of available git hooks in the manpage githooks . There is no hook for git rebase --continue (the list is exhaustive).
There is a "post-rewrite" hook that is "called by commands that overwrite", such as git rebase . However, it only starts after the command is executed (i.e., when the redirect is completed).
It will provide you with a list of new commits created by rewriting, so you can check to see if there are any conflict markers committing and complain, but at this point it is too late to cancel rebase. You can still return rebase using reflog, of course.
In general, it may be easier to write some shell for git rebase or a separate verification tool for calling manually. In any case, you should (IMHO) always review your changes before calling git rebase --continue . If you adhere to this, you will not have accidentally marked conflict markers.
sleske
source share