I agree that this is confusing and +1 on clarifying this -- thanks for tackling this 📖,@jdpace ! 💟

I'm not that familiar with how services work so I might very well be wrong on this, but there might be confusion around what the hook listens to by default vs what it can listen to if configured manually. By default, itlistens to just thepush andpull_request events, but as far as I can tell -- itcan be configured to listen to other events as well (as perhttps://github.com/github/github-services/blob/master/CONTRIBUTING.md#other-hook-types)

If my understanding is correct, what do you think about clarifying this difference?

If my understanding is correct, what do you think about clarifying this difference?

Correct, a service may support many more events besides it's default set. Services set up via the UI only get the default set specified in the service file (orpush if not specified). It's probably worth clarifying the difference here.

@jdpace How about something like this:

Active hooks can be configured to trigger for one or more service supported events. In other words, the service must support listening for the event you want to trigger.

For example, the Web service supports listening for all events, while the IRC service can listen forpush,issues andpull_request events.

Each service also has a set of default events for which it listens if it isn't configured. For example, the Web service listens only forpush events by default, while the IRC service listens onpush andpull_requests events. Service hooks set up via the Webhooks UI listen only for the default set of events, but can bere-configured via the API.

Not sure if this is helpful -- I'm finding it hard to write a clear explanation. 😓

For example, the Web service supports listening for all events, while the IRC service can listen forpush,issues andpull_request events.

IRC actually supports several more than that which might lead to more confusion. Here's a couple of other popular services which only support a limited number of events:

• Twitter -push
• Email -public,push

Service hooks set up via the Webhooks UI listen only for the default set of events, but can be re-configured via the API.

"Webhooks UI" isn't the right term here. "UI" is more correct but might not be specific enough.

Hallo

Von Samsung Mobile gesendet

-------- Ursprüngliche Nachricht --------
Von: Jared Pacenotifications@github.com
Datum:
An: "github/developer.github.com"developer.github.com@noreply.github.com
Cc: Maiksteppin@live.de
Betreff: Re: [developer.github.com] Fix reference to default IRC hook events. (#496)

For example, the Web service supports listening for all events, while the IRC service can listen for push, issues and pull_request events.

IRC actually supports several more than that which might lead to more confusion. Here's a couple of other popular services which only support a limited number of events:

Twitter - push
Email - public, push
Service hooks set up via the Webhooks UI listen only for the default set of events, but can be re-configured via the API.

"Webhooks UI" isn't the right term here. "UI" is more correct but might not be specific enough.

—
Reply to this email directly or view it on GitHub.

@jdpace Thanks for pointing those things out. 🙇 Here's a new version which takes those two things into account:

Active hooks can be configured to trigger for one or more service supported events. In other words, the service must support listening for the event you want to trigger.

For example, the Web service supports listening for all events, while theIRC service can listen forpush,issues,pull_request,commit_comment,pull_request_review_comment, andissue_comment events.

Each service also has a set of default events for which it listens if it isn't configured. For example, the Web service listens only forpush events by default, while the IRC service listens onpush andpull_requests events. Service hooks set up via the repository settings UI listen only for the default set of events, but can bere-configured via the API.

What do you think?

@izuzak That looks great to me 📖 ✨

Cool, I updated the PR with that text. 👯