Denying new GitHub Services
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 toweb
for webhooks, or the name of any valid service. Starting today, this endpoint does not requirename
to be provided; if it is, it will only acceptweb
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!