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

# GitHub Issues

Link customer issues in Pylon to issues in GitHub

## [​](https://docs.usepylon.com/product-ticketing/github#setup)Setup <a href="#setup" id="setup"></a>

Click into the App Directory from your Pylon dashboard and then click on the GitHub integration to view setup instructions.

## [​](https://docs.usepylon.com/product-ticketing/github#usage)Usage <a href="#usage" id="usage"></a>

## [​](https://docs.usepylon.com/product-ticketing/github#creating-tickets)Creating GitHub Issues <a href="#creating-tickets" id="creating-tickets"></a>

You can create an issue via the Kanban board or via the triage channel.

1. Via Kanban: From a Pylon issue, you’ll see a GitHub Details module in the sidebar. Select the team you’d like to create the ticket in, and click Create.

<figure><img src="https://mintlify.s3-us-west-1.amazonaws.com/pylon/images/product-ticketing-create-or-search.png" alt=""><figcaption></figcaption></figure>

2. Via Triage channel: when conversational tickets are posted in your triage channel and product ticketing is enabled, you’ll see a `Create Ticket 📦` button.

<figure><img src="https://mintlify.s3-us-west-1.amazonaws.com/pylon/images/gh-1.png" alt=""><figcaption></figcaption></figure>

Clicking it will allow you to select which GitHub repo to create the issue in, along with a pre-filled AI-generated title.

<figure><img src="https://mintlify.s3-us-west-1.amazonaws.com/pylon/images/gh-2.png" alt=""><figcaption></figcaption></figure>

After clicking `Create` you’ll now see a link to the GitHub Issue.

<figure><img src="https://mintlify.s3-us-west-1.amazonaws.com/pylon/images/gh-3.png" alt=""><figcaption></figcaption></figure>

The created GitHub Issue will include a link to the Slack conversation.

<figure><img src="https://mintlify.s3-us-west-1.amazonaws.com/pylon/images/gh-4.png" alt=""><figcaption></figcaption></figure>

### Linking GitHub Issues <a href="#try-it-out" id="try-it-out"></a>

You can also search for a GitHub issue by keywords or identifier, or directly paste in a link to the issue.

### Inside Pylon

Comments in GitHub sync as internal notes to Pylon and comments on the GitHub internal thread from Pylon sync back to GitHub as comments on the ticket.

In addition, when a GitHub issue is completed, the Pylon issue receives a notification and gets moved to "On You", letting you know to tell the customer about the completed change.


---

# 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.usepylon.com/pylon-docs/integrations/ticketing/github-issues.md?ask=<question>&goal=<user_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.