From: Junio C Hamano <gitster@pobox.com>
To: Phillip Wood <phillip.wood123@gmail.com>
Cc: Sean Allred <allred.sean@gmail.com>, Git List <git@vger.kernel.org>
Subject: Re: rebase invoking pre-commit
Date: Tue, 26 Dec 2023 08:33:12 -0800 [thread overview]
Message-ID: <xmqqa5pwkjp3.fsf@gitster.g> (raw)
In-Reply-To: <bf1ce173-50d7-405f-88c1-7edb7ec5a55a@gmail.com> (Phillip Wood's message of "Fri, 22 Dec 2023 10:05:56 +0000")
Phillip Wood <phillip.wood123@gmail.com> writes:
> On 21/12/2023 20:58, Sean Allred wrote:
>> Is there a current reason why pre-commit shouldn't be invoked during
>> rebase, or is this just waiting for a reviewable patch?
>
> The reason that we don't run the pre-commit hook is that the commit
> being rebased may have been created with "git commit --no-verify" and
> so running the pre-commit hook would stop it from being rebased - see
> e637122ef2 (rebase -m: do not trigger pre-commit verification,
> 2008-03-16).
Very true. And back then we didn't have "rebase -x" mechanism but
these days, anybody who is interested in running a command between
each step can use it to run any validation script, not the one with
fixed name called "hooks", so I'd place this to fairly low priority.
Thanks.
next prev parent reply other threads:[~2023-12-26 16:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-21 20:58 rebase invoking pre-commit Sean Allred
2023-12-22 10:05 ` Phillip Wood
2023-12-22 22:05 ` Sean Allred
2023-12-26 16:33 ` Junio C Hamano [this message]
2023-12-23 21:37 ` Elijah Newren
2023-12-31 10:52 ` Sean Allred
2024-01-05 4:59 ` Elijah Newren
2024-01-05 16:26 ` Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqa5pwkjp3.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=allred.sean@gmail.com \
--cc=git@vger.kernel.org \
--cc=phillip.wood123@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).