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

# Git source control

{% hint style="info" %}
Contact our support team about the possibility of enabling Git on your plan.
{% endhint %}

UI Bakery self-hosted provides you with the same features as cloud regarding Git source control. For more details, you can visit this [section](/concepts/source-control.md).

But self-hosted also allows you to do more, specifically:

* [Connect multiple UI Bakery instances to the same Git repository](/on-premise/git-source-control/managing-multi-instance-deployment.md)
* [Create a customized URL for your pull requests](/on-premise/git-source-control/custom-pr-url.md)
* Automate your [GitHub](/on-premise/git-source-control/automate-github-releases.md)/[GitLab](/on-premise/git-source-control/automate-gitlab-releases.md)/[Bitbucket](/on-premise/git-source-control/automate-bitbucket-releases.md) releases

{% hint style="warning" %}
Make sure to [add](/on-premise/install-and-update/recommendations/generate-custom-secrets.md) the `UI_BAKERY_PROJECT_PRIVATE_KEY_SECRET` variable for Git to work in the self-hosted version.&#x20;
{% endhint %}


---

# 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.uibakery.io/on-premise/git-source-control.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.
