Deprecating GitHub Notification Endpoint, Migrating to Webhooks

In 2018 we introduced a custom GitHub API endpoint to receive webhook payloads and convert them to notifications. Earlier this year we introduced full webhook support which enables extracting custom data, allowing you to listen to more GitHub event types and customizing notifications.

In light of this, we are deprecating Pushover’s custom GitHub API endpoint and encouraging all users to migrate to this new webhook mechanism. We will be completely removing the GitHub API endpoint later this year.

Migrating

To migrate your existing GitHub API URLs to Pushover webhooks, login to your dashboard and click Create a Webhook next to Your Webhooks.

To duplicate the existing GitHub API endpoint (which only supported the “push” event), enter the following field information:

• Title Selector: {{pusher.name}} pushed to {{repository.name}}
• Body Selector: {{commits.last.message}}
• URL Selector: {{commits.last.url}}
• URL Title Selector: View commit on GitHub

Of course, feel free to change these however you want. You can then customize the notification settings such as selecting a delivery group or setting a custom sound.

Once you give your webhook a name and save it, you will be given a new custom URL that should be used in place of the existing https://api.pushover.net/1/github/... URL in your GitHub projects.

Since Pushover webhooks are free to create, you can create additional ones to support GitHub webhook events other than just “push” by matching different data in the body selector. If the body selector evaluates to an empty string, no notification is sent.