> 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-a-tfs-branch.md).

# Creation of a TFS Branch

### Creation of a TFS Branch <a href="#creation-of-a-tfs-branch" id="creation-of-a-tfs-branch"></a>

1. Log in to your ARM account.
2. Go to the **`VC Repo's`**` ``tab.`
3. Select a TFS 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-1677743406990.png" alt=""><figcaption></figcaption></figure>
5. In the **`Create Branch`** screen, enter a branch name in the **`Display Name`**&#x66;ield.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. Under the **`Target URL`** field, do the following:
   1. The **`Repository`** field is auto-filled.
   2. Enter your **`Project Name`**.
   3. Enter your **`Branch`** name.
8. Under the **`Parent URL`** field, do the following:
   1. The **`Repository`** field is auto-filled.
   2. Enter the **`Project Name`** from which data is to be fetched.
   3. Enter your **`Branch`** name.
9. Click **`Create`**.<br>

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

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

1. On the **`VC Repo's`** page, select a TFS repository from the **`Repository List`**.
2. Click on **`Register`**.<br>

   <figure><img src="https://cdn.document360.io/8711f4e7-c040-4616-aac9-d947f87e4619/Images/Documentation/image-1677743540438.png" alt=""><figcaption></figcaption></figure>
3. On the next screen, enter the **`Display Name`** of the branch that 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 URL entered when registering the repository.
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-1677743591460.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-a-tfs-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.