> For the complete documentation index, see [llms.txt](https://docs.kodesage.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kodesage.ai/integrations/git.md).

# Git

Git integration overview

For version control, Kodesage uses SSH keys to securely clone repositories and process the codebase, enabling detailed analysis and documentation generation.

**Integration process**

1. **Setup SSH Keys:** Ensure SSH keys are added to the Git repository to establish a trusted connection for cloning. 
2. **Repository Addition:** Add the Git repository to Kodesage through the secure ingestion process. 
3. **Code Analysis:** Kodesage processes the repository's content, breaking it down into manageable segments for analysis and documentation generation. 

**How to connect a Git repistory to Kodesage**

You will need to go to Data sources - Upload codebase. Once there, you will be able to either:

* Upload a ZIP file directly
* connect to an SSH Git Repository
* connect to a HTTPS Git Repistory

<figure><img src="https://1498950825-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F8qhVWzMLXcYl3WBsXBHs%2Fuploads%2FGBMJ7eC6ziDlfNq66YRm%2FXnapper-2025-01-29-18.20.45.png?alt=media&amp;token=c56f9613-9547-43b5-aff8-250c4cf39655" alt=""><figcaption></figcaption></figure>


---

# 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.kodesage.ai/integrations/git.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.