Re: [PATCH] rebase --no-verify
Nanako Shiraishi <nanako3@lavabit.com> wrote:
Show 6 quoted lines
> It is sometimes desirable to disable the safety net of pre-rebase hook
> when the user knows what he is doing (for example, when the original
> changes on the branch have not been shown to the public yet).
>
> This teaches --no-verify option to git-rebase, which is similar to the way
> pre-commit hook is bypassed by git-commit.
> It probably is better to fix "rebase -i" to share more code with the main
> "rebase" script to avoid duplicated run-pre-rebase-hook function, but it
> is beyond what I can do right now. Perhaps people more smart and
> beautiful than me can help (^_^;)
True. But its already a mess. git-sequencer is probably the
right approach to merge it all together.
> git-rebase--interactive.sh | 10 +++++++++-
> git-rebase.sh | 7 ++++++-
> t/t3409-rebase-hook.sh | 16 ++++++++++++++++
> 3 files changed, 31 insertions(+), 2 deletions(-)
--
Shawn.
Shawn O. Pearce <spearce@spearce.org>