Denying new GitHub Services

October 1, 2018
gjtorikian

As we announced back in April, starting today, additional GitHub Services cannot be added to any repository on GitHub.com, via the UI or API. You can continue to edit or delete existing GitHub Services. For more information, see "Replacing GitHub Services."

Ensure that your repositories use newer APIs available for handling events according to the following changes that will take place:

Currently, the "Create a repository webhook" endpoint accepts a required argument called name, which can be set to web for webhooks, or the name of any valid service. Starting today, this endpoint does not require name to be provided; if it is, it will only accept web as a valid value.
For the week of November 5th, 2018, there will be a week-long brownout for GitHub Services. Any GitHub Service installed on a repository will not receive any payloads. Normal GitHub Services operations will resume at the conclusion of the brownout.
On January 31, 2019, we will permanently stop delivering all installed services' events on GitHub.com.

Please contact us if you have any questions!

This content may be out of date. For the newest content, see the API posts on the GitHub Blog. All of GitHub's Docs are now in one place! You can see Apps, REST API, and GraphQL API on GitHub Docs.

Denying new GitHub Services

This content may be out of date. For the newest content, see the API posts on the GitHub Blog.

All of GitHub's Docs are now in one place! You can see Apps, REST API, and GraphQL API on GitHub Docs.