> For the complete documentation index, see [llms.txt](https://knowledgebase.autorabit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledgebase.autorabit.com/product-guides/arm/registration/version-control-branch/git-branch-creation.md).
# GIT Branch Creation
### Overview
Developers can create a branch to work on a new version of an existing application. Changes in the primary or other branches will only affect your branch if you pull the latest changes from those branches.
Creating a new branch for each task is a common practice because it allows others to identify what changes to expect and, for backtracking purposes, to understand why a particular code change is implemented.
### Creation of a GIT Branch
1. Log in to your ARM account.
2. From the ARM home page, click on the **`Admin`** module and go to the **`VC Repo's`** tab.
3. Select a **GIT** repository for which the branch needs to be created.Note:If your GIT repository is **nCino** enabled, the nCino logo will be marked in front of your repository.
4. Under **`Branches`**, click on **`Create`** button.
5. In **`Create Branch`** screen, give a **`Branch name`** and select **`Parent Branch`** and **`Branch Type`** from the list. If the **`Parent Branch`** configures a metadata folder path, the same configuration will map to the newly created branch.
{% hint style="info" %}
**Point to Note**: The characters **"//" \ , \* ? & ' " < > | \` \~ ( )** and **space** are not allowed in the **`Branch Name`** field.
{% endhint %}
6. Click **`Create`** to complete the creation process.
### Registration of an existing GIT branch
1. On the **`VC Repo's`** page, select a GIT repository from the repositories list.
2. Click **`Register`**.
3. Checkbox the branches you need to register and enter the following details:
* **`Parent Branch:`** Choose its parent branch from the drop-down.
* **`Last commit date`**: The last commit date is fetched from Salesforce Org in EZ-Commit based on the specified date.
4. Once done, click **`Register`** to complete the branch registration.
### Registration of nCino configured GIT branch
1. On the **`Version Control Repositories`** page, select a GIT repository marked with the **`nCino`** logo.
2. Click **`Register`**.
3. Checkbox the branches you need to register and select its **`Parent Branch`** and last commit date *(the last commit date is used to fetch changes from Salesforce Org in EZ-Commit based on the specified date).*
4. Click the **`Register`** button to complete the branch registration.
---
# 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://knowledgebase.autorabit.com/product-guides/arm/registration/version-control-branch/git-branch-creation.md?ask=&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.
