> 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/creation-of-svn-branch.md).

# Creation of an SVN Branch

### Creation of SVN Branch <a href="#creation-of-svn-branch" id="creation-of-svn-branch"></a>

1. Log in to your ARM account.
2. Go to the **`VC Repo's`** tab.
3. Select the SVN repository for which the branch needs to be created.
4. Click on **`Create`** button.<br>

   <figure><img src="https://cdn.document360.io/8711f4e7-c040-4616-aac9-d947f87e4619/Images/Documentation/image-1677740889482.png" alt=""><figcaption></figcaption></figure>
5. In the **`Create Branch`** screen, give the branch a name in the **`Display Name`** field.Point to Note:The characters **"//" \ , \* ? & ' " < > | \` \~ ( )** and **space** are not allowed in the **`Display Name`** field.
6. Select your **`Credential`** from the drop-down field.
7. In the **`Branch URL`** field, enter the branch name beside the parent branch. ***For example,*** *branches/Development*.
8. **`Parent URL`** is auto-filled; however, you can modify it (if necessary).&#x20;
9. Click **`Create`** to complete the creation process.<br>

   <figure><img src="https://cdn.document360.io/8711f4e7-c040-4616-aac9-d947f87e4619/Images/Documentation/image-1677741239425.png" alt="" width="375"><figcaption></figcaption></figure>

### Registration of an existing SVN branch <a href="#registration-of-an-existing-svn-branch" id="registration-of-an-existing-svn-branch"></a>

1. On the **`VC Repo's`** page, select one SVN repository from the **`Repository List`**.<br>

   <figure><img src="https://cdn.document360.io/8711f4e7-c040-4616-aac9-d947f87e4619/Images/Documentation/image-1677740959030.png" alt=""><figcaption></figcaption></figure>
2. Click **`Register`**.
3. On the next screen, enter the **branch name** you want to register in ARM.Point to Note:The characters **"//" \ , \* ? & ' " < > | \` \~ ( )** and **space** are not allowed in the **`Display Name`** field.
4. The **`Repository`** field is auto-filled with the repository root. Give a branch name beside the parent branch. ***For example,*** *branches/Integration*.
5. Select the **`Last Commit Date`**. The last commit date fetches changes from Salesforce org in EZ-Commit based on the specified date.
6. Click **`Register`** to complete the registration of the branch.<br>

   <figure><img src="https://cdn.document360.io/8711f4e7-c040-4616-aac9-d947f87e4619/Images/Documentation/image-1677741338967.png" 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://knowledgebase.autorabit.com/product-guides/arm/registration/version-control-branch/creation-of-svn-branch.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.