# GitHub advanced settings

ilert’s GitHub advanced settings allow fine-grained management of repository events, like failed workflows or security alerts. You control the alert filters, labeling, and routing to ensure only relevant triggers notify the correct engineers, improving signal quality and reducing alert fatigue.

1. Click on GitHub settings to show the advanced settings.

<figure><img src="/files/ZzWm8h7nDc7WKNAQuGZs" alt="" width="563"><figcaption></figcaption></figure>

2. You may now choose one of the given **Event Types** which this alert source should process. (leaving the selection on 'Select' will result the alert source to process all incoming **Event Types**)\
   Supported **Event Types** are: `Issues, Check run, Code scanning alert, Secret scanning alert, Secret scanning alert location, Dependabot alert`.
3. Now select any **Action Types** which this alert source should process. The **Action Types** selection is based on the selected **Event Type**.

<figure><img src="/files/nZ4jsyY5VGNWMNCnQ7Qg" alt="" width="563"><figcaption></figcaption></figure>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.ilert.com/integrations/inbound-integrations/github/advanced-settings.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.