Add information about the wildcard event

kdaigle · izuzak · commit 6e857893a92c · 2014-02-24T18:11:05.000+01:00
diff --git a/content/changes/2014-02-24-wildcard-event-for-webhooks.md b/content/changes/2014-02-24-wildcard-event-for-webhooks.md
@@ -0,0 +1,14 @@
+---
+kind: change
+title: Wildcard Event for Webhooks
+created_at: 2014-2-24
+author_name: kdaigle
+---
+
+We've made a small change to make it easier for webhook integrators to receive "everything".
+Instead of adding every event to your webhook, you can now opt-in to all events (including
+all new events in the future) by using the [wildcard event](/webhooks/#wildcard-event) (`*`).
+
+If you add this event to an existing webhook, we'll remove the existing specific events and
+send you payloads for all supported events. As we add new events, you'll automatically
+begin receiving those too.
diff --git a/content/webhooks/index.md b/content/webhooks/index.md
@@ -77,6 +77,7 @@ Name | Description
 `status` | Any time a Repository has a status update from the API
 `deployment` | Any time a Repository has a new deployment created from the API.
 `deployment_status` | Any time a deployment for the Repository has a status update from the API.
+`*` | Any time any event is triggered ([Wildcard Event](#wildcard-event)).
 
 
 ### Payloads
@@ -86,6 +87,13 @@ types](/v3/activity/events/types/), with the exception of [the original `push`
 event](http://help.github.com/post-receive-hooks/),
 which has a more detailed payload.
 
+## Wildcard Event
+
+We also support a wildcard (`*`) that will match all supported events. When you
+add the wildcard event, we'll replace any existing events you have configured with
+the wildcard event and send you payloads for all supported events. You'll also
+automatically get any new events we might add in the future.
+
 ## Ping Event
 
 When you create a new webhook, we'll send you a simple `ping` event to let you
