Like many other Version Control Systems, Git has a way to fire off custom scripts when certain important actions occur. There are two groups of these hooks: client side and server side. The client-side hooks are for client operations such as committing and merging. The server-side hooks are for Git server operations such as receiving pushed commits. You can use these hooks for all sorts of reasons, and you\u2019ll learn about a few of them here.<\/p>\n
Installing a Hook<\/p>\n
The hooks are all stored in the hooks subdirectory of the Git directory. In most projects, that\u2019s .git\/hooks. By default, Git populates this directory with a bunch of example scripts, many of which are useful by themselves; but they also document the input values of each script. All the examples are written as shell scripts, with some Perl thrown in, but any properly named executable scripts will work fine \u2014 you can write them in Ruby or Python or what have you. These example hook files end with .sample; you\u2019ll need to rename them.<\/p>\n
To enable a hook script, put a file in the hooks subdirectory of your Git directory that is named appropriately and is executable. From that point forward, it should be called. I\u2019ll cover most of the major hook filenames here.<\/p>\n
Client-Side Hooks<\/p>\n
There are a lot of client-side hooks. This section splits them into committing-workflow hooks, e-mail-workflow scripts, and the rest of the client-side scripts
\nRegards,
\nRajesh Kumar
\nTwitt me @ twitter.com\/RajeshKumarIn<\/a><\/p>\n\n