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

# GitHub

Send any bug report or recording to GitHub in a few clicks.

Screendesk adds the capture link and debugging context automatically.

{% hint style="info" %}
This page covers the manual **Send to app** action. Folder automations create issues automatically when recordings or bug reports enter a folder.
{% endhint %}

### Before you start

* You need edit access on the Screendesk item.
* Connect GitHub from **Profile → Integrations**.
* Each teammate uses their own GitHub account.

### Connect GitHub

{% stepper %}
{% step %}

### Open integrations

In Screendesk, go to **Profile → Integrations**.
{% endstep %}

{% step %}

### Connect GitHub

Find **GitHub** and click **Connect**.

Approve Screendesk in GitHub.
{% endstep %}

{% step %}

### Return to Screendesk

GitHub now appears in your connected apps list.

You can also start this flow from **Send to app → Connect GitHub**.
{% endstep %}
{% endstepper %}

### Create a GitHub issue

{% stepper %}
{% step %}

### Open the item

Open the bug report or recording in Screendesk.

Click **Send to app**.
{% endstep %}

{% step %}

### Choose GitHub

Select **GitHub issue**.

If GitHub is your only connected app, the main button may say **Send to GitHub**.
{% endstep %}

{% step %}

### Review fields

Check the title and description.

Choose a **Repository**.

Optionally add labels, assignees, and a milestone.
{% endstep %}

{% step %}

### Create the issue

Click **Create issue**.

Screendesk keeps the GitHub issue link on the item, even if you disconnect later.
{% endstep %}
{% endstepper %}

### Available fields

| Field       | Required | Notes                                              |
| ----------- | -------: | -------------------------------------------------- |
| Title       |      Yes | Used as the GitHub issue title.                    |
| Description |      Yes | Your notes are added above the Screendesk context. |
| Repository  |      Yes | The repository where the issue will be created.    |
| Labels      |       No | Labels load from the selected repository.          |
| Assignees   |       No | Assignees load from the selected repository.       |
| Milestone   |       No | Milestones load from the selected repository.      |

### What Screendesk sends

* A direct link to the bug report or recording
* The source website URL, when available
* Device and browser details
* The capture timestamp in UTC
* A link to developer information in Screendesk

Anything you add in the description goes above the generated Screendesk context.

### Customize the form

Click **Edit fields** in the GitHub modal to show or hide optional fields.

Required fields stay visible.

Your field choices are saved for your GitHub connection.

### Permissions

* You must be able to edit the bug report or recording.
* Watch-only users cannot connect personal app accounts or send items to GitHub.
* Workspace admins can remove GitHub from **Profile → Integrations** for the whole workspace. Existing issue links stay visible.

<details>

<summary>Troubleshooting</summary>

**GitHub is not in the Send to app menu**

Open **Profile → Integrations** and connect GitHub.

If the button is missing entirely, confirm that you can edit the bug report or recording.

**The repository list is empty**

Make sure your GitHub account can access the repository you want to use.

Then reconnect GitHub from **Profile → Integrations**.

**Labels, assignees, or milestones do not load**

Confirm the selected repository has those options available and that your GitHub account has permission to read them.

</details>


---

# 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.screendesk.io/bug-reports/send-to-apps/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.