> For the complete documentation index, see [llms.txt](https://docs.siit.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.siit.io/integrations/ticketing/github.md).

# GitHub

### What you get

* **One-click escalation from any request.** Click **Escalate ticket** in the request side panel, pick a GitHub repository and labels, and a linked issue is created with the Siit context pre-filled.
* **Workflow-driven issue creation.** Use **Create GitHub issue** as a workflow step, with approval gating where needed.
* **Audit trail.** Every GitHub action triggered from Siit is recorded on the request timeline.

### How it works

1. From the request side panel, click **Escalate ticket** and pick **GitHub**.
2. Choose the repository, labels, assignees, and milestone (optional). Fill in the title and description.
3. Submit. Siit creates the GitHub issue, links it back to the Siit request, and posts the link on both sides.

The same flow is available in workflows (as a **Create GitHub issue** action).

### What syncs from GitHub

* **Issues created from Siit** — every escalated ticket is tracked with its GitHub issue number, repository, and link.
* **Links** — preserved between the Siit request and the GitHub issue, visible on both sides.

> **Note** — bi-directional status sync is not currently available for GitHub. Track resolution either through the GitHub link on the request or by manually closing the Siit request when the issue is closed.

### Custom field mapping

> **Coming soon.** Custom field mapping for GitHub is on our roadmap. For now, you can set the standard issue fields (title, description, labels, assignees, milestone) when escalating. To track which fields are exposed, reach out via the in-app chat.

### Connect GitHub

1. In Siit, go to **Settings → Integrations**, find **GitHub** in the Ticketing section, and click **Connect**.
2. Sign in to GitHub as an admin and approve the requested scopes.
3. Pick the organization and repository(ies) available for escalation.
4. Test by escalating a sample request from Siit to GitHub.

Need a more detailed walkthrough? Reach out to support via the in-app chat.

### Common workflows

**Bug report auto-escalation.** *Trigger: Service = "App bug report". Actions: Create GitHub issue in the engineering repo → Add label "bug" → Notify requester.*

**Infrastructure request.** *Trigger: Tag "infra" added. Actions: Manager approval → Create GitHub issue in the infra repo → Notify requester.*

### Troubleshooting

**"Authorization failed" on connect.** The admin signing in lacks org admin rights, or the org restricts third-party app installs. Try with an org owner.

**Repository missing from the destination picker.** The Siit GitHub user lacks access to that repository. Update repo permissions in GitHub and re-sync.

**"Issue created" but no link in Siit.** The GitHub issue was created but the back-link save failed. Open the request timeline — the GitHub issue number is logged. Manually re-link if needed.


---

# 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.siit.io/integrations/ticketing/github.md?ask=<question>&goal=<endgoal>
```

`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.