Automatic Updates with Push-to-Deploy

With Push-to-Deploy enabled, WP Pusher can automagically update your plugins or themes every time new code is pushed to your Git repositories.

Automatic updates

If you enable Push-to-Deploy for a plugin or theme, WP Pusher will setup a webhook on GitHub or Bitbucket (you need to do this manually in GitLab) that will fire every time new code is pushed. This webhook will then call the Push-to-Deploy URL to trigger an update.

By default, a webhook is triggered every time code is pushed, no matter which branch. If you want to fine tune this, you can manually configure which events are triggering the webhook on GitHub, Bitbucket or GitLab. For example, you could have a webhook fire only when a pull request has been merged or when a new release has been created.

Read more about automatic updates in these specific guides covering:

The Push-to-Deploy URL and continuous integration

The Push-to-Deploy URL is a secret URL that you shouldn't normally share with anyone, since it contains a secret token. When someone or something sends a request to this URL, an update is triggered. This is neat if you have some kind of continuous integration flow where you want other things to trigger updates. You can use the Push-to-Deploy URL in any place that can perform an HTTP request.


See the troubleshooting guide for more information.

Need any help?

If you have any questions about WP Pusher, Git or WordPress, our email is Don't hesitate shooting us a message! You can also click the little ❤️ in the corner of this page.