From: Phillip Wood <phillip.wood123@gmail.com>
To: Alex Riesen <alexander.riesen@cetitec.com>,
Phillip Wood <phillip.wood@dunelm.org.uk>
Cc: Junio C Hamano <gitster@pobox.com>, Jeff King <peff@peff.net>,
Git List <git@vger.kernel.org>
Subject: Re: [PATCH] Document positive variant of commit and merge option "--no-verify"
Date: Mon, 1 Nov 2021 15:34:57 +0000 [thread overview]
Message-ID: <918977fe-4e87-8a2d-c337-6b57b83ae8dc@gmail.com> (raw)
In-Reply-To: <YXv7CW4QHQOzFla6@pflmari>
Hi Alex
On 29/10/2021 14:45, Alex Riesen wrote:
> From: Alex Riesen <raa.lkml@gmail.com>
>
> This documents "--verify" option of the commands. It can be used to re-enable
> the hooks disabled by an earlier "--no-verify" in command-line.
>
> Signed-off-by: Alexander Riesen <raa.lkml@gmail.com>
> ---
This version looks good, thanks for documenting these options
Best Wishes
Phillip
> Phillip Wood, Fri, Oct 29, 2021 15:32:16 +0200:
>> On 28/10/2021 16:44, Alex Riesen wrote:
>>> diff --git a/Documentation/git-commit.txt b/Documentation/git-commit.txt
>>> index a3baea32ae..2268787483 100644
>>> --- a/Documentation/git-commit.txt
>>> +++ b/Documentation/git-commit.txt
>>> @@ -174,9 +174,14 @@ The `-m` option is mutually exclusive with `-c`, `-C`, and `-F`.
>>> -n::
>>> --no-verify::
>>> - This option bypasses the pre-commit and commit-msg hooks.
>>> + By default, pre-commit and commit-msg hooks are run. When one of these
>>
>> As I suggested yesterday I think this would be better if it kept the "the"
>> from the original text as you do below for the merge documentation -
>> s/default, /&the /
>
> Updated:
>
> -n::
> --[no-]verify::
> By default, the pre-commit and commit-msg hooks are run.
> When any of `--no-verify` or `-n` is given, these are bypassed.
> See also linkgit:githooks[5].
>
>>> --- a/Documentation/merge-options.txt
>>> +++ b/Documentation/merge-options.txt
>>> @@ -112,8 +112,9 @@ option can be used to override --squash.
>>> +
>>> With --squash, --commit is not allowed, and will fail.
>>> ---no-verify::
>>> - This option bypasses the pre-merge and commit-msg hooks.
>>> +--[no-]verify::
>>> + By default, the pre-merge and commit-msg hooks are run.
>>> + When `--no-verify` is given, these are bypassed.
>>> See also linkgit:githooks[5].
>>
>> This text looks good. It would be nice to be consistent when documenting
>> "--verify" and "--no-verify" so that documentation for commit and merge both
>> have either a separate entry for each option as you have for commit or a
>> shared entry as you have here for merge. I'd be tempted to use this form in
>> the commit documentation.
>
> So I did.
>
> Regards,
> Alex
>
> Documentation/git-commit.txt | 5 +++--
> Documentation/merge-options.txt | 5 +++--
> t/t7504-commit-msg-hook.sh | 8 ++++++++
> 3 files changed, 14 insertions(+), 4 deletions(-)
>
> diff --git a/Documentation/git-commit.txt b/Documentation/git-commit.txt
> index a3baea32ae..b27a4c4c34 100644
> --- a/Documentation/git-commit.txt
> +++ b/Documentation/git-commit.txt
> @@ -173,8 +173,9 @@ The `-m` option is mutually exclusive with `-c`, `-C`, and `-F`.
> (see http://developercertificate.org/ for more information).
>
> -n::
> ---no-verify::
> - This option bypasses the pre-commit and commit-msg hooks.
> +--[no-]verify::
> + By default, the pre-commit and commit-msg hooks are run.
> + When any of `--no-verify` or `-n` is given, these are bypassed.
> See also linkgit:githooks[5].
>
> --allow-empty::
> diff --git a/Documentation/merge-options.txt b/Documentation/merge-options.txt
> index 80d4831662..80267008af 100644
> --- a/Documentation/merge-options.txt
> +++ b/Documentation/merge-options.txt
> @@ -112,8 +112,9 @@ option can be used to override --squash.
> +
> With --squash, --commit is not allowed, and will fail.
>
> ---no-verify::
> - This option bypasses the pre-merge and commit-msg hooks.
> +--[no-]verify::
> + By default, the pre-merge and commit-msg hooks are run.
> + When `--no-verify` is given, these are bypassed.
> See also linkgit:githooks[5].
>
> -s <strategy>::
> diff --git a/t/t7504-commit-msg-hook.sh b/t/t7504-commit-msg-hook.sh
> index 31b9c6a2c1..67fcc19637 100755
> --- a/t/t7504-commit-msg-hook.sh
> +++ b/t/t7504-commit-msg-hook.sh
> @@ -130,6 +130,14 @@ test_expect_success '--no-verify with failing hook' '
>
> '
>
> +test_expect_success '-n followed by --verify with failing hook' '
> +
> + echo "even more" >> file &&
> + git add file &&
> + test_must_fail git commit -n --verify -m "even more"
> +
> +'
> +
> test_expect_success '--no-verify with failing hook (editor)' '
>
> echo "more stuff" >> file &&
>
next prev parent reply other threads:[~2021-11-01 15:35 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-26 12:11 [PATCH] Fix "commit-msg" hook unexpectedly called for "git pull --no-verify" Alex Riesen
2021-10-26 21:16 ` Jeff King
2021-10-27 6:35 ` [PATCH v2] " Alex Riesen
2021-10-27 9:06 ` Jeff King
2021-10-27 12:09 ` [PATCH] " Alex Riesen
2021-10-27 12:19 ` Jeff King
2021-10-27 13:27 ` [PATCH] Remove negation from the merge option "--no-verify" Alex Riesen
2021-10-27 20:16 ` Junio C Hamano
2021-10-28 6:38 ` Alex Riesen
2021-10-28 8:04 ` [PATCH] Remove negation from the commit and " Alex Riesen
2021-10-28 13:57 ` Phillip Wood
2021-10-28 15:44 ` Alex Riesen
2021-10-28 15:46 ` [PATCH 2/2] Fix "commit-msg" hook unexpectedly called for "git pull --no-verify" Alex Riesen
2021-10-28 16:51 ` Junio C Hamano
2021-10-28 17:16 ` Alex Riesen
2021-10-28 19:25 ` Junio C Hamano
2021-10-29 6:34 ` Alex Riesen
2021-10-28 15:49 ` [PATCH] Remove negation from the commit and merge option "--no-verify" Alex Riesen
2021-10-29 13:32 ` Phillip Wood
2021-10-29 13:45 ` [PATCH] Document positive variant of " Alex Riesen
2021-11-01 15:34 ` Phillip Wood [this message]
2021-10-27 20:12 ` [PATCH] Fix "commit-msg" hook unexpectedly called for "git pull --no-verify" 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=918977fe-4e87-8a2d-c337-6b57b83ae8dc@gmail.com \
--to=phillip.wood123@gmail.com \
--cc=alexander.riesen@cetitec.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.net \
--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 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).