Git in Automations
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 a 'Git Connect' process within the Automations page and follow the prompts to link to 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 'Pull & Connect' button. This allows synchronization of automations across different instances or workspaces of UI Bakery.
Execution behavior under Git
Once Git is connected, Automations execution is not affected by the branch changes until the changes are merged, pulled, and released in the main branch. This means that developers can safely modify the Automations code and settings in parallel.
The following rules are applied for Automations depending on a branch:
Main Branch:
The main branch is read-only and cannot be edited to avoid merge conflicts.
The main branch typically reflects the production or primary version of your Automations.
Only Automations in the main branch can be executed through CRON jobs.
Feature Branches:
You can create and work on different branches for developing new features or testing.
Enable and configure CRON settings and Webhooks configuration.
Automations in these branches can be triggered via webhooks and the builder, allowing testing and iteration.
CRON jobs are not executed from feature branches until they are merged into the main branch and released, if release process in used.
Last updated