> 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/extras/automations/git-in-automations.md).

# Git in automations

The **Git integration** feature allows you to synchronize, manage versions, and collaborate on your Automations projects more effectively. This guide will walk you through the process of connecting your Automations to a Git repository and highlight the key functionalities this integration offers.

## Getting started with Git Integration

### Connecting to an Empty Project

To connect Automations to a new Git repository, simply initiate the *Git Connect* process within the Automations page and follow the prompts to link your Git repository.

### Connecting to an Existing Git Project

If your Git project already has existing automations, you can import them from Git. To do this, follow the *Git Connect* process and use the **Pull & Connect** button. This allows you to synchronize automations across different instances or workspaces of UI Bakery.

## Execution behaviour under Git

Once Git is connected, Automations **execution won't be affected by branch changes** until these changes are merged, pulled, and released to the main branch. This means that developers can safely modify the Automations code and settings in parallel.

The following rules apply to Automations depending on the branch:point\_down:

| Main branch                                                                                                  | Feature branch                                                                                                                                                                                                                                                                                                                                                                   |
| ------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| <ul><li><strong>Read-only</strong> and cannot be edited to avoid merge conflicts</li></ul>                   | <ul><li>You can create and work on different branches for developing new features or testing</li></ul>                                                                                                                                                                                                                                                                           |
| <ul><li>Typically reflects the <em>production</em> or <em>primary</em> version of your Automations</li></ul> | <ul><li>You can enable and configure CRON settings and Webhooks configuration</li></ul>                                                                                                                                                                                                                                                                                          |
| <ul><li>Automations <strong>CAN</strong> be executed through CRON jobs</li></ul>                             | <ul><li>CRON jobs are <strong>NOT</strong> executed until they are the feature branch is merged into the main branch and released, if the <a href="/extras/automations/environment-and-release-strategy.md">release process</a> is used.<br><br>Instead, Automations can be triggered via <em>webhooks</em> and the <em>Builder</em>, allowing testing and iterations.</li></ul> |


---

# 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/extras/automations/git-in-automations.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.