我正在查看一个 Git Hook ，它在 Python 代码中查找打印语句。如果找到打印语句，它会阻止 Git 提交。

我想覆盖这个钩子(Hook)，我被告知有一个命令可以这样做。我没能找到它。有什么想法吗？

最佳答案

也许(来自 git commit man page ):

git commit --no-verify -m "commit message"
           ^^^^^^^^^^^
-n  
--no-verify

This option bypasses the pre-commit and commit-msg hooks. See also githooks(5).

正如 Blaise 评论的那样, -n 可以对某些命令有不同的作用。
例如，git push -n其实就是一个dry-run push。
只有 git push --no-verify 会跳过钩子(Hook)。

注意:Git 2.14.x/2.15 改进了 --no-verify 行为:

参见 commit 680ee55 (2017 年 8 月 14 日)Kevin Willford (``) .
^{(由 Junio C Hamano -- gitster -- merge 于 commit c3e034f ，2017 年 8 月 23 日)}

commit: skip discarding the index if there is no pre-commit hook

"git commit" used to discard the index and re-read from the filesystem just in case the pre-commit hook has updated it in the middle; this has been optimized out when we know we do not run the pre-commit hook.

Davi Lima指出in the comments git cherry-pick 不支持--no-verify。
因此，如果 cherry-pick 触发了预提交 Hook ，您可能会像 this blog post 中那样，必须以某种方式评论/禁用该 Hook ，以便您的 git cherry-pick 继续。

在 merge 冲突解决后的 git rebase --continue 情况下，需要相同的过程。

在 Git 2.36(2022 年第 2 季度)中，run_commit_hook() 的调用者可以了解它“成功”是因为 Hook 成功还是因为没有任何 Hook 。

参见 commit a8cc594 (固定为 commit 4369e3a1 )，commit 9f6e63b (2022 年 3 月 7 日)Ævar Arnfjörð Bjarmason (avar) .
^{(由 Junio C Hamano -- gitster -- merge 于 commit 7431379，2022 年 3 月 16 日)}

hooks: fix an obscure TOCTOU "did we just run a hook?" race

^{Signed-off-by: Ævar Arnfjörð Bjarmason}

Fix a Time-of-check to time-of-use (TOCTOU) race in code added in 680ee55 ("commit: skip discarding the index if there is no pre-commit hook", 2017-08-14, Git v2.15.0-rc0 -- merge listed in batch #3).

This obscure race condition can occur if we e.g. ran the "pre-commit" hook and it modified the index, but hook_exists() returns false later on (e.g., because the hook itself went away, the directory became unreadable, etc.).
Then we won't call discard_cache() when we should have.

The race condition itself probably doesn't matter, and users would have been unlikely to run into it in practice.
This problem has been noted on-list when 680ee55 was discussed, but had not been fixed.

Let's also change this for the push-to-checkout hook.
Now instead of checking if the hook exists and either doing a push to checkout or a push to deploy we'll always attempt a push to checkout.
If the hook doesn't exist we'll fall back on push to deploy.
The same behavior as before, without the TOCTOU race.
See 0855331 ("receive-pack: support push-to-checkout hook", 2014-12-01, Git v2.4.0-rc0 -- merge) for the introduction of the previous behavior.

This leaves uses of hook_exists() in two places that matter.
The "reference-transaction" check in refs.c, see 6754159 ("refs: implement reference transaction hook", 2020-06-19, Git v2.28.0-rc0 -- merge listed in batch #7), and the "prepare-commit-msg" hook, see 66618a5 ("sequencer: run 'prepare-commit-msg' hook", 2018-01-24, Git v2.17.0-rc0 -- merge listed in batch #2).

In both of those cases we're saving ourselves CPU time by not preparing data for the hook that we'll then do nothing with if we don't have the hook.
So using this "invoked_hook" pattern doesn't make sense in those cases.

The "reference-transaction" and "prepare-commit-msg" hook also aren't racy.
In those cases we'll skip the hook runs if we race with a new hook being added, whereas in the TOCTOU races being fixed here we were incorrectly skipping the required post-hook logic.

关于git - 跳过 Git 提交钩子(Hook)，我们在Stack Overflow上找到一个类似的问题： https://stackoverflow.com/questions/7230820/