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

# Connecting Github App to Rubicon

Rubicon stores the SQL files in your Github account and integrates with Github to make it easier for you to develop, test and maintain your model files.. We recommend you create a separate repo for Rubicon. Rubicon will create a folder called "`Rubicon`" in the repo you connect to Rubicon to save the models.

In Github, follow these steps to create a personal access token that allows access to your repository.

1. In the upper-right corner of any page, click on your profile photo, then click **Settings**.
2. Click **Developer Settings**
3. Click the **Personal access tokens** tab.
4. Click the **Generate new token** button
5. Enter a token description
6. Select the **repo** scope and **workflow** scope, and click the **Generate token** button. **workflow** scope is needed in case your repository has GitHub Action workflows.
7. Copy the token to your clipboard. You enter this token in Rubicon under **Settings > Git integration**.


---

# 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.rubicon.io/documentation/connecting-github-app-to-rubicon.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.