> For the complete documentation index, see [llms.txt](https://docs.secoda.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.secoda.co/enterprise/self-hosted-secoda/additional-resources/additional-environment-variables/github-application-on-premise.md).

# Github Application (on-premise)

To configure a Github App for use within Secoda,

* **Access Account Settings**:
  * Click your profile photo in the upper-right corner of any GitHub page.
  * For a personal account:
    * Click **Settings**.
  * For an organization account:
    * Click **Your organizations**.
    * Next to the organization, click **Settings**.
* **Navigate to Developer Settings**:
  * In the left sidebar, click **Developer settings**.
  * Then, click **GitHub Apps**.
* **Create a New GitHub App**:
  * Click **New GitHub App**.
* **Configure the App**:
  * **Name**: Enter a clear and concise name for your app (up to 34 characters). This name must be unique across GitHub.
* **Set Permissions and Subscribe to Events**:
  * Under **Permissions**, select the following permissions:
    * Pull requests: Read and write
    * Profile: Read and write
    * Contents: Read and write
    * Metadata: Read only
  * Under **Subscribe to events**, select the webhook events your app should receive:
    * Pull request
* **Define Installation Scope**:
  * Under **Where can this GitHub App be installed?**, choose **Only on this account** or **Any account**.
* **Create the App**:
  * Click **Create GitHub App** to finalize the registration.
    * Generate a client secret and private key.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.secoda.co/enterprise/self-hosted-secoda/additional-resources/additional-environment-variables/github-application-on-premise.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.