> 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/~/changes/vPSzQFfkdJCVWGT5AL1m/outbound-integrations/github-issue.md).
# GitHub Outbound Issue Integration
## In Github: Create an ilert user and create an API token
1. Optional: Create a dedicated ilert user in Github. This has the advantage that you can distinguish the Github tickets created by ilert.
2. Go to **Profile Settings** --> **Developer settings** --> **Personal access tokens**, and click **Generate new token**.
3. Give it a name and select **Repo Scope** for the token
4. Click on **Create**. Keep your API key for later, as it is needed in ilert.
## In ilert: Create a Github Connector and link to an alert source
1. Click on the gear icon → **Connectors**
2. Click on **Add Connector**
2. Select **Github** as **type** and fill in all fields. Enter a name and the API key from above.
3. **Go to** the alert sources tab and open the alert source whose alerts you want to publish in Github. Click on **Incident actions → Create alert action**.
4. Select **Github** as the **type** then select the connector created in step 3 and fill in all fields. In the **Owner** and the **Repository** fields specify the owner and repository of the Github project where the ilert alerts should be published as Github Issue.
5. Finished! You can now test the alert action by clicking on the button **Test this connection**. Then a test issue will be published in the respective Github project.
## FAQ
**Are updates to an alert published in the Github Ticket?**
Yes, the state of the ilert Incident is reflected in the title of the Github ticket, eg. \[RESOLVED] Host compute.infra is DOWN.
**Can I choose which updates should be published to an alert in Github?**
Currently not. If you wish we are looking forward to reading your feedback via chat or e-mail.
## Related articles
{% content-ref url="/pages/-M9OVt0ROtWvj2I\_XFj2" %}
[GitHub Inbound Issue Integration](/~/changes/vPSzQFfkdJCVWGT5AL1m/inbound-integrations/github/inbound-issue.md)
{% endcontent-ref %}
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.ilert.com/~/changes/vPSzQFfkdJCVWGT5AL1m/outbound-integrations/github-issue.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.