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

# Git integration

Connect Zerve to your Git provider to version your projects.

Connect Zerve to your Git provider to save your projects' code to a repository, track history, work on branches and use code from your repositories in your blocks.

## Supported providers

| Provider                                                | Setup guide                                                                                           |
| ------------------------------------------------------- | ----------------------------------------------------------------------------------------------------- |
| **GitHub** (cloud)                                      | [GitHub (cloud)](/zerve-docs/git-and-version-control/git/github-cloud.md)                             |
| **GitHub Enterprise Server**                            | [GitHub Enterprise Server](/zerve-docs/git-and-version-control/git/github-enterprise-server.md)       |
| **Bitbucket Cloud**, with access tied to a user account | [Bitbucket OAuth consumer](/zerve-docs/git-and-version-control/git/bitbucket-oauth-consumer.md)       |
| **Bitbucket Cloud**, with access to a whole workspace   | [Bitbucket Cloud Connect app](/zerve-docs/git-and-version-control/git/bitbucket-cloud-connect-app.md) |
| **Azure DevOps Repos**                                  | [Azure DevOps Repos](/zerve-docs/git-and-version-control/git/azure-devops-repos.md)                   |

## Individual or organization?

You can connect a Git provider for yourself, or for your whole organization.

| Install for           | Use it when                                                                    | Where                                                                              |
| --------------------- | ------------------------------------------------------------------------------ | ---------------------------------------------------------------------------------- |
| **Yourself**          | You only need your own repositories, or you're working in a personal space     | Your profile picture → **Individual Settings** → **Git Integration**               |
| **Your organization** | Your team works on shared repositories, and you want central control of access | The organization selector → your organization → **Settings** → **Git Integration** |

## What you can do

Once connected, you can:

* **Commit** a project's code to a repository and branch
* **See commit history**, and compare versions block by block
* **Create branches** to work on changes safely
* **Open pull requests**, and pull merged changes back into the main project
* **Restore** an earlier version of a project
* **Include repositories** in your blocks, so you can import shared code

See [Source control in notebooks](/zerve-docs/git-and-version-control/source-control-in-notebooks.md).


---

# 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.zerve.ai/zerve-docs/git-and-version-control/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.