Git Hooks is powerful tool for customizing Git. In this post we created custom post-commit hook, that send email after every new commit.
Client side hooks
- pre-commit is called before a commit occurs.
- prepare-commit-msg lets you edit the default message before the editor is fired up; it's useful in automated commits to add some context.
- commit-msg is the last step where you can interrupt a commit.
- post-commit is executed after a commit is completed, for notification purposes.
- post-checkout you can use it to set up your working directory properly for your project environment.
- post-merge you can use it to restore data in the working tree that Git can’t track, such as permissions data.
Server side hooks
- pre-receive can be used to check and interrupt the receival of the new commits, if it is the case.
- post-receive notifies that commits have been published on this repository.
- update is a version of pre-receive that is run once per each different branch.
- post-update is a notification activated after all references have been updated; the default hook updates some metadata to let the repository be published via HTTP.
For detailed description and other not mentioned hooks go to git documentation.
There are already published some post-receive hook for sending email after push new data to server (1, 2, 3).
Send emails after commit on the client side is not typical use case. On Linux servers we let store the /etc in a Git. After changing the configuration we commit changes to ( for the server local ) git repository. After every configuration changing we want to notify the other administrators. We use the following post-commit hook:
After copy a new post-commit file to .git/hooks don’t remember reinit git:
#git init
