> For the complete documentation index, see [llms.txt](https://docs.ilert.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ilert.com/integrations/inbound-integrations/github/advanced-settings.md).
# GitHub advanced settings
Use ilert's GitHub advanced integration to customize alert handling, filter notifications, and route technical events to the right on-call teams.
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.
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**.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.ilert.com/integrations/inbound-integrations/github/advanced-settings.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
