# GitHub

If you connect external services to Alli Coworker, the assistant can directly use your team tools during conversations. Only users with administrator permissions can manage integrations.

{% hint style="info" %}
**Tip**: If you connect GitHub, the assistant can access repository issues, pull requests, and code through the GitHub connector within the app during Slack/Teams bot conversations and app creation workflows.
{% endhint %}

<figure><img src="/files/SVeGbWDQO4i6tWtxX5nA" alt=""><figcaption></figcaption></figure>

## GitHub Connection - Issuing a GitHub Personal Access Token (PAT)

GitHub integrates using a Personal Access Token (PAT). The permissions (scopes) you select when creating the token determine what actions the assistant can perform.

**Fine-grained PAT (recommended)** — allows you to precisely specify access to particular repositories and permissions.

{% stepper %}
{% step %}

## Go to the GitHub token creation page

<figure><img src="/files/Ft7HiSH5Z4JVH8F63UNu" alt=""><figcaption></figcaption></figure>

Go to GitHub → Settings → Developer settings → Personal access tokens → Fine-grained tokens. ([GitHub Guide](https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/managing-your-personal-access-tokens))
{% endstep %}

{% step %}

## Create a new token

<figure><img src="/files/Og5UaINNJvDwmHsA58Gv" alt=""><figcaption></figcaption></figure>

Click “Generate new token”
{% endstep %}

{% step %}

## Select the repositories you want to grant access to

<figure><img src="/files/5VWai7GyvNsnlH5wHulO" alt=""><figcaption><p>Fine-grained tokens</p></figcaption></figure>

Select the repositories you want to grant access to.
{% endstep %}

{% step %}

## Set permissions

Configure the following permissions.

| Permissions   | Level          | Purpose                                 |
| ------------- | -------------- | --------------------------------------- |
| Issues        | Read and write | View, create, and update issues         |
| Pull requests | Read and write | View, create, and review pull requests  |
| Contents      | Read-only      | Code search                             |
| Metadata      | Read-only      | Basic repository information (required) |
| {% endstep %} |                |                                         |

{% step %}

## Save the token

Generate the token and copy it for safekeeping.

**⚠️ Note: You can only view the full token once immediately after it is created. Make sure to copy it before registering it.**
{% endstep %}
{% endstepper %}

<figure><img src="/files/uIcCbO0sfzoBKhKeUvpT" alt=""><figcaption><p>Tokens(classic)</p></figcaption></figure>

> 💡 If using a Classic PAT: Go to GitHub → **Settings → Developer settings → Personal access tokens → Tokens (classic)** and generate a token, then select the **repo** scope.

## Register in Alli Coworker&#x20;

<figure><img src="/files/NBl4CFKfGNbiJ2FJxqfx" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/80i31IJKtAKSOJ5FgWjg" alt=""><figcaption></figcaption></figure>

1. On the integrations page, click the “Connect” button on the GitHub card.
2. Enter the GitHub API key you generated.
3. Click the “Connect” button.

<figure><img src="/files/fMChfF3tO9BCM3RfFLKN" alt=""><figcaption></figcaption></figure>

4. Once the connection is complete, an “Active” badge will appear at the top of the card, along with the key fingerprint (last 4 characters) and the registration date.

## Managing integration status

Connected service cards include three buttons.

<table><thead><tr><th width="270.1669921875">버튼</th><th>동작</th></tr></thead><tbody><tr><td><strong>갱신</strong></td><td>API 키를 교체합니다. 이전 키는 즉시 무효화됩니다</td></tr><tr><td><strong>비활성화 / 활성화</strong></td><td>키를 삭제하지 않고 연동을 일시적으로 끄거나 켭니다</td></tr><tr><td><strong>연결 해제</strong></td><td>저장된 API 키를 완전히 삭제합니다. 이 작업은 되돌릴 수 없습니다</td></tr></tbody></table>

{% hint style="warning" %}
⚠️ Note: When you renew the key, the previous key will become invalid immediately. Make sure to prepare the new key before renewing.
{% endhint %}

### How do I use GitHub after connecting it?

#### Request directly from Slack · Teams bots

<figure><img src="/files/hjyRHud7zr0a9971j7Vj" alt=""><figcaption></figcaption></figure>

If GitHub is connected, you can naturally request repository actions in plain language without additional setup:

* “Show me the list of PRs merged this week.”
* “Find open bug issues.”
* “Create a new issue: title ○○, label bug.”
* “Check the review status of PR #42.”
* “Search for code related to login.”

#### Using GitHub issues and PRs when creating apps

<figure><img src="/files/mK3aiHfujWFm8lu7M6jD" alt=""><figcaption></figcaption></figure>

When you request an app to be built, you can use GitHub issues or pull requests as context. The bot will directly read the issue title, description, and comments to understand requirements, so you don’t need to re-enter the information.

> “Create an app based on issue #123 in repository ○○.”
>
> **⚠️ Note: This approach only references GitHub at the time the app is created. If you want a completed app to access GitHub at runtime, you must configure a separate PAT in the app code.**


---

# 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://docs.allganize.ai/alli-coworker-en/connector/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.