All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sean Allred <allred.sean@gmail.com>
To: phillip.wood@dunelm.org.uk
Cc: Sean Allred <allred.sean@gmail.com>, Git List <git@vger.kernel.org>
Subject: Re: rebase invoking pre-commit
Date: Fri, 22 Dec 2023 16:05:20 -0600	[thread overview]
Message-ID: <m01qbdx561.fsf@epic96565.epic.com> (raw)
In-Reply-To: <bf1ce173-50d7-405f-88c1-7edb7ec5a55a@gmail.com>


Phillip Wood <phillip.wood123@gmail.com> writes:
> [...], we'd need to add something like "git rebase --continue
> --no-verify" as a way to bypass it when resolving conflicts in commits
> that were created with "git commit --no-verify".

Looks like such a flag already exists to skip the 'pre-rebase' hook.
Presumably it can pull double-duty to skip pre-commit as well.

(It's a little messy to me to not be able to pick/choose which hooks to
skip, but looks like this is already status quo with other hooks.)

--
Sean Allred

  reply	other threads:[~2023-12-22 22:07 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 [this message]
2023-12-26 16:33   ` Junio C Hamano
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=m01qbdx561.fsf@epic96565.epic.com \
    --to=allred.sean@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=phillip.wood@dunelm.org.uk \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.