Katsushi Kawamori

<h4>Search of hooks</h4>
<ul>
<li>Ascending order by first_call.</li>
<li>Search by hook_name is possible.</li>
<li>Search by called_by is possible.</li>
</ul>

Hooks View

Jared Cobb

If you have a build / deployment process for your site, it’s often useful to have a way to execute code in your theme or plugins after you commit or deploy your code changes.
GitHub, Bitbucket, and Beanstalk are common tools that allow you to configure a webhook URL that gets called as soon as you make a check-in or deployment.
Common uses are
<ul>
<li>Purge the cache after you deploy new theme code (WP Super Cache or W3 Total Cache)</li>
<li>After you build your JavaScript/CSS, trigger a backup of the live site</li>
<li>Trigger any WordPress hook</li>
<li>Run any other plugin or theme code you wish!</li>
</ul>
More information on how to use this plugin (including how to setup GitHub, Bitbucket, and Beanstalk) can be found at <a href="http://jaredcobb.com/post-deployment-hook" rel="nofollow ugc">http://jaredcobb.com/post-deployment-hook</a>
The plugin is also <a href="https://github.com/jaredcobb/post-deployment-hook" rel="nofollow ugc">hosted on GitHub</a>. Pull requests are welcome!

Post Deployment Hook

Creates a webhook listener in WordPress, useful for integrating a post-deployment hook from your build / deployment process

Hooks View vs Post Deployment Hook