# GitHub

{% hint style="warning" %}
Integrations is a part of the Custom plan. Additional cost might apply.
{% endhint %}

The GitHub integration connects Suptask ticketing with your software development workflow. When a support ticket requires engineering attention, you can link it directly to a GitHub issue - keeping support agents and developers in sync without leaving Slack.

**Use cases with Suptask:**

* Automatically create GitHub issues from Suptask tickets that require development work.
* Link existing GitHub issues to Suptask tickets for full context.
* Keep support agents updated on issue status and comments without switching tools.

***

### Requirements

You need a [GitHub](https://github.com) account and a **Personal Access Token (classic)** to set up the integration.

The token must belong to a GitHub user with access to the repositories you want to connect.

***

### Generate a Personal Access Token in GitHub

1. Log in to [github.com](https://github.com) and click your **profile photo** in the upper-right corner.
2. Go to **Settings**.
3. In the left sidebar, scroll down and click **Developer settings**.
4. Click **Personal access tokens** → **Tokens (classic)**.
5. Click **Generate new token** → **Generate new token (classic)**.
6. Give the token a descriptive name, such as **Suptask Integration**.
7. Set an **expiration** — Suptask recommends selecting **No expiration** or a long-lived date to avoid interruptions.
8. Under **Select scopes**, enable the following:

   | Scope      | Why it's needed                                             |
   | ---------- | ----------------------------------------------------------- |
   | `repo`     | Full access to repositories (issues, comments, status)      |
   | `read:org` | Read organization membership (required for org-level repos) |
9. Click **Generate token**.
10. **Copy the token immediately** — GitHub will not show it again.

{% hint style="warning" %}
Store the token securely. Anyone with this token can access your repositories with the permissions granted above.
{% endhint %}

***

### Share the Token with Suptask

Once you have your token, pass it to the Suptask Integrations Specialist (SIS):

1. Share the **Personal Access Token** securely with your SIS contact.
2. Include the **GitHub username** associated with the token.
3. Include the **repository URL(s)** you want to connect, e.g.:\
   `https://github.com/your-org/your-repo`

{% hint style="info" %}
The integration will be enabled for a specific Inbox or Form of your choice.
{% endhint %}

***

### Example of how it works

1. A ticket is created in Suptask via Slack.
2. An agent reviews the ticket and decides it needs engineering work.
3. The agent triggers a GitHub issue creation directly from the Suptask ticket in Slack.
   * This can also happen automatically for every ticket created in a specific Inbox.
4. A GitHub issue is created and linked to the Suptask ticket.
5. Comments and status updates are synced between Suptask and GitHub.
6. Agents can reply and track progress directly in Slack - no need to switch to GitHub.

***

### How to get started

The GitHub integration is set up and enabled together with the Suptask Integrations Specialists (SIS).

{% hint style="info" %}
Contact Suptask Support for more information and to get started.
{% endhint %}


---

# Agent Instructions: 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:

```
GET https://support.suptask.com/integrations-automations-and-workflows/integration-guides/github.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.