Webhook events can have multiple actions. As GitHub's feature set grows, the list of actions may change. Ensure that your application explicitly checks the action before doing any processing. For example, the [`IssuesEvent`](https://developer.github.com/v3/activity/events/types/#issuesevent) has several possible actions, such as `opened` when the issue is created, `closed` when the issue is closed, and `assigned` when the issue is assigned to someone.

Two code examples are given below, Fig 1.1 and Fig 1.2. In Fig 1.1, the `process_closed` method will be called for any event action which is not `opened` or `assigned`. This means that the `process_closed` method will be called for events with the `closed` action, but also other events with different actions delivered to the webhook.

Instead, the suggested approach is to explicitly check event actions and act accordingly such as in Fig 1.2. In this example the `closed` action is checked first before calling the `process_closed` method.

**Fig 1.1: Not Recommended: catch-all else block**

case action

when "opened"

process_opened

when "assigned"

process_assigned

process_closed

**Fig 1.2: Recommended: explicitly check each action**

case action

when "opened"

process_opened

when "assigned"

process_assigned

when "closed"

process_closed

We may also add new webhook event types from time to time. If your webhook is configured to "Send me everything" then your code should also explicitly check for the event type in a similar way as we have done with checking for the action type above.