Git鉤子用于在提交、推送等操作前后自動運(yùn)行腳本以執(zhí)行任務(wù)。具體用途包括：1. 提交前運(yùn)行代碼檢查或測試；2. 強(qiáng)制提交信息格式；3. 推送后發(fā)送通知。它們有助于統(tǒng)一團(tuán)隊(duì)規(guī)范并減少手動步驟，例如阻止測試失敗時的提交。Git鉤子位于倉庫中的.git/hooks/目錄下，默認(rèn)不共享，需手動復(fù)制或使用工具如Husky進(jìn)行團(tuán)隊(duì)協(xié)作。編寫基本鉤子需創(chuàng)建可執(zhí)行文件并命名對應(yīng)事件，例如pre-commit，并在其中寫入邏輯判斷以阻止或允許操作。

You can create a custom Git hook by placing a script in your .git/hooks directory. These hooks run automatically before or after events like commit, push, and receive. The trick is to name the file correctly and make it executable.

What are Git hooks used for?

Git hooks are scripts that Git executes before or after key actions, such as committing or pushing. They're useful for automating tasks like:

• Running linters or tests before commits
• Enforcing commit message formats
• Sending notifications after pushes

They help enforce team standards and reduce manual steps. For example, a pre-commit hook might stop you from committing if tests fail.

Where do I find Git hooks?

All Git hooks live in the .git/hooks/ folder inside your repository. If you navigate there, you’ll see some sample files like pre-commit.sample or prepare-commit-msg.sample.

To use one, just remove the .sample extension and make the file executable with:

chmod  x .git/hooks/pre-commit

You can also create new ones — just name them after the event they should trigger on, like post-push or pre-rebase.

How to write a basic Git hook

Let’s say you want a hook that checks for large files before each commit (to avoid accidentally adding big binaries). Here's how you'd do it:

1. Create a new file: .git/hooks/pre-commit
2. Add a shebang at the top, like #!/bin/bash
3. Write your logic — here’s a simple version:

#!/bin/bash
# Prevent committing files larger than 5MB
find . -type f -size  5M | grep -v ".git" && echo "Large files detected — commit denied." && exit 1
exit 0

4. Save and make it executable with chmod x .git/hooks/pre-commit

Now, any attempt to commit a file over 5MB will be blocked. You can customize this script to check for file types, code formatting, or anything else you need.

Can Git hooks be shared across teams?

By default, Git hooks aren’t shared when you clone a repo — they live only in your local .git/hooks folder. So yes, you can share them, but not automatically.

One common approach is to put your hooks in a hooks/ directory in the project root and have teammates symlink or copy them into .git/hooks/. Some teams use tools like Husky (for Node.js) or other frameworks to manage this more easily.

Alternatively, you can add a setup script that copies hooks into place when someone runs npm install or similar.

基本上就這些。

以上是如何創(chuàng)建自定義git鉤？的詳細(xì)內(nèi)容。更多信息請關(guān)注PHP中文網(wǎng)其他相關(guān)文章！