Announcing the deprecation of GitHub Services

GitHub plans on shutting down GitHub Services so we can shift focus to other areas of the API, such as strengthening GitHub Apps and GraphQL, and improving webhooks. The intention of GitHub Services was to allow third-party developers to submit code for integrating with their services, but this functionality has been superseded by GitHub Apps and webhooks. GitHub Services has not supported new features since April 25, 2016, and we plan to officially deprecate it on October 1st, 2018.

Move to webhooks using GitHub or OAuth apps

As part of the deprecation process, we need integrators on our platform to move from HTTP-based services over to plain webhooks. Webhooks are much easier for both users and GitHub staff to debug on the web because of improved logging.

We have been coordinating with our largest integrators to assist them in seamlessly transitioning from GitHub Services to GitHub Apps and webhooks. In order to move your integration over to plain webhooks, you can leverage either GitHub or OAuth apps. Both "Replacing GitHub Services" and "Differences between GitHub Apps and OAuth Apps" provide information regarding the differences between the two frameworks.

Learn more about replacing GitHub Services

To learn more about this deprecation or moving from GitHub Services to GitHub or OAuth apps, check out Replacing GitHub Services.

Deprecation timeline

Updated 01-29-19

  • May 31, 2018: Submit your intentions for migrating or replacing your GitHub Service.
  • October 1, 2018: GitHub discontinues allowing users to install services. GitHub Services will be removed from the UI.
  • January 29, 2019: As an alternative to the email service, you can now start using email notifications for pushes to your repository. See "About email notifications for pushes to your repository" in the GitHub Help documentation to learn how to configure commit email notifications.
  • January 31, 2019: GitHub stops delivering installed services' events on