> 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/concepts/source-control/getting-started.md).

# Git controls overview

Take a quick look at the Git controls in UI Bakery :point\_down:

<figure><img src="https://837703843-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUX6zPRMFFK0yrTghj7cY%2Fuploads%2FEXCRnhWnRNRZflnwXxyF%2FCleanShot%202026-01-19%20at%2013.18.54%402x.png?alt=media&amp;token=a4aa6381-bf67-425a-9830-e3171e3eb6c3" alt=""><figcaption></figcaption></figure>

1. **Branches selector** - switch between branches
2. **Sync branches** - sync the list of branches with UI Bakery
3. **Pull/Force pull** - pull the latest changes from the selected branch/force pull current branch changes to UI Bakery

{% hint style="warning" %}
*Force pull* action overwrites your local uncommitted changes with the current remote branch. It can be helpful in situations where automatic project model updates or conflicting Git changes prevent a standard pull or revert.
{% endhint %}

4. **Commit & Push** - commit and push the changes to the selected branch
5. **Open Pull Request** - create a pull request for the selected branch

## Changing the default branch

Some teams may be working on the same project and it may not be convenient to share the same `main` branch. In such cases, you can set a specific branch as the **default** one for your team only. \
\
You can do this by opening the *Git* tab in the footer panel and clicking the **Set current branch as default** button. Once set, the system will operate in the following way:

* The project will automatically load from this branch.
* It will become the base branch for all new branches.
* It will be used as the default target for `pull` requests.
* It will act the source branch when duplicating projects.
* If Git is disconnected, the state will revert to the default branch's state.
* The default branch cannot be deleted from the database (ID-based).

<figure><img src="https://837703843-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUX6zPRMFFK0yrTghj7cY%2Fuploads%2FryJiZb24eHMwpaDKEfto%2FCleanShot%202026-01-19%20at%2013.57.06%402x.png?alt=media&amp;token=0e7f3432-6999-41e6-b950-50ced3eac56c" 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.uibakery.io/concepts/source-control/getting-started.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.