# GitHub

Here you will find a step-wise guide to set up Typo.

Setting up your Git provider account is the first step of the onboarding process.&#x20;

### Step 1: Connect Git

Navigate to <https://typoapp.io/> > Get Started with Git provider as GitHub

<div align="left"><figure><img src="/files/MHC5bIX5akd41exQfV3b" alt="" width="563"><figcaption></figcaption></figure></div>

### Step 2: Permission to your GitHub Repos

Select GitHub and you will land on the GitHub authorization page

> You need to have Admin access to your GitHub account to complete these steps.

<div align="left"><figure><img src="/files/MaL74co461yiG3FknEH3" alt="" width="563"><figcaption></figcaption></figure></div>

{% hint style="info" %}
🚀 Tip - we only take read-only access. All the insights are generated based on metadata
{% endhint %}

### **Step 3: Continue with the Onboarding Process**

Once you complete the authorization step, the next step is to enter your details

The next step is to connect your Issue Tracker, followed by optionally connecting Slack. You can also complete these steps later from the Settings section. For more details, read about [Issue tracker integration here.](/typo-help-docs/getting-started/integrations/issue-tracker.md)

You will now be landed on your dashboard and your first level of insights will be published in a few minutes. You can further customize your teams and integrations from the dashboard settings & integration section.

<br>


---

# 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://typo.gitbook.io/typo-help-docs/getting-started/integrations/git/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.
