git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] hooks: introduce 'hooks.allowNoVerify' configuration

From
Junio C Hamano <gitster@pobox.com>
Date
Sep 2, 2026, 19:21 UTC
Message-ID
<xmqqa4pzihnm.fsf@gitster.g>
In-Reply-To
<pull.2215.git.1788365862670.gitgitgadget@gmail.com>
"Alessio Attilio via GitGitGadget" <gitgitgadget@gmail.com> writes:
Show 5 quoted lines
> From: Alessio Attilio <alessio.attilio@protonmail.com>
>
> Introduce 'hooks.allowNoVerify' as an opt-in workflow guardrail to
> prevent accidental bypass of hooks with '--no-verify' when set to false.
> Authoritative enforcement remains server-side.
Accidental
	$ git foo --no-verify

may be prevented by setting this configuration variable, but then would we need another layer of protection to prevent accidental

	$ git -c hooks.allownoverify foo --no-verify

by introducing another configuration variable to forbid hooks.allownoverify to be overriden?

I do not think we want to go into this slipperly slope. Thanks for sending a patch, but I am personally not interested.

Besides, verifications that users may be tempted to bypass, but want to instill discipline to prevent bypassing, may not be implemented as hooks, and the way they are bypassed may not be "--[no-]verify" command line option. When one wants a way to prevent such verifications from getting disabled, the mechanism should also allow forbidding verification that is built into the system from getting disabled. Limiting a settings to hooks is probably not a good idea, and introducing a new "hooks." hierarchy for this setting is not something we want to see.

Previous: Alessio Attilio via GitGitGadget
Message 6 of 6 in “hooks: introduce 'hooks.allowNoVerify' configuration”
  1. hooks: introduce 'hooks.allowNoVerify' configurationAlessio Attilio via GitGitGadget, Sep 2, 2026
  2. hooks: introduce 'hooks.allowNoVerify' configurationAlessio Attilio via GitGitGadget, Sep 2, 2026
  3. hooks: introduce 'hooks.allowNoVerify' configurationAlessio Attilio via GitGitGadget, Sep 2, 2026
  4. brian m. carlsonSep 2, 2026
  5. hooks: introduce 'hooks.allowNoVerify' configurationAlessio Attilio via GitGitGadget, Sep 2, 2026
  6. Junio C HamanoSep 2, 2026

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.