# Version Control Repositories Summary

{% hint style="info" %}
**Important Note**: This article is for the **Org Administrator** in particular. The actions discussed in the article will not be available to general users.
{% endhint %}

### Overview <a href="#overview" id="overview"></a>

The lists of repositories you have added yourself and any other repositories your team members have shared can be seen on the **`VC Repo's`**` ``(`**`Version Control Repository)`** page.

Repositories with **Salesforce DX** enabled will have![](/files/2k7sBSuvLd8djNcMaeNc)icon displayed, and nCino objects configured will have![](/files/is2qVKLdUNN5XPMuqee2)icon beside their repository under **`Repositories List`** for easier identification.

<div align="center"><figure><img src="/files/BhD2qiAKe4xHMSPZrecu" alt="" width="264"><figcaption></figcaption></figure></div>

<figure><img src="/files/znqYZJGS9Dd65TnWDpTS" alt="" width="375"><figcaption></figcaption></figure>

For each version control repository registered in ARM, the following information or fields are displayed:

Create a pull request to propose and collaborate on changes to a repository. This is discussed later.&#x20;

| Field Name             | Description                                                                                                                                       |
| ---------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------- |
| `Repository Name`      | Name of your  version control repository                                                                                                          |
| `Type`                 | Version control repository type, i.e., GIT, TFS, or SVN.                                                                                          |
| `URL`                  | Repository URL                                                                                                                                    |
| `Created Date`         | Date and time stamp for repository created or modified                                                                                            |
| `Credentials`          | User's credential linked with the version control repository                                                                                      |
| `Test Connection`      | This will allow you to check whether the connection has been authenticated. A success message is displayed after the authentication is completed. |
| `Enable nCino app`     | On selection, the nCino objects will get registered with the current repository.                                                                  |
| `Pull Request Support` | Create a pull request to propose and collaborate on changes to a repository. This is discussed later.                                             |

<figure><img src="/files/dMaqyVvY0be3O9z1jSvs" alt=""><figcaption></figcaption></figure>

#### Pull Request Support <a href="#pull-request-support" id="pull-request-support"></a>

Create a pull request to propose and collaborate on changes to a repository. These changes are proposed in a branch, which ensures that the master branch only contains finished and approved work. You can specify which branch you'd like to merge your changes into when you create your pull request.

<figure><img src="/files/CMighnve0B6QJ7KDKGXl" alt=""><figcaption></figcaption></figure>

Pull requests can only be opened between two branches that are different. More detailed instructions are available in a separate article; please refer [HERE](/product-guides/arm/arm-features/version-control/external-pull-request.md).

#### Branches/Tags <a href="#branchestags" id="branchestags"></a>

The Git tags created or branches registered for the version control repository will get displayed under the **`Branches/Tags`** section. For more information about Git Tags, check out the link [HERE](broken://pages/Rx3Lff7EWqWNQnf3nABV).

**Additional details under Branch**

**A. Create a Branch**

Create a new branch for the current repository. Newly created branches will get listed under the **`Branches`** tab. ([LEARN MORE](/product-guides/arm/arm-features/version-control/introduction-to-version-control/version-control-branch-workflow.md))

<figure><img src="/files/RfwVicXWFUpt7nnHiAzh" alt=""><figcaption></figcaption></figure>

**B. Register a Branch**

Register an existing branch to the current repository. ([LEARN MORE](/product-guides/arm/arm-features/version-control.md))

<figure><img src="/files/k8HsCW5kD0op7aDnoD7A" alt="" width="563"><figcaption></figcaption></figure>

<figure><img src="/files/FJMI328F2sIhHZZT0BHB" alt=""><figcaption></figcaption></figure>

**C. Unregister a Branch**

Select a branch or branches to unregister them from your version control system. Upon confirmation, the branch(es) gets permanently deleted from your version control system. The entire data will get erased.

<figure><img src="/files/FJtcPWjfDBXgQiJaobE6" alt=""><figcaption></figcaption></figure>

**D. Sync Branches**

The **`Sync Branches`** option will allow you to view the branches that are no longer available in your version control repositories but present in ARM; therefore, you can delete them from the ARM application.

**E. Branch Details:**

For each branch, view the following details:

<figure><img src="/files/lbZDs3Y22o3AK4Of1ur9" alt=""><figcaption></figcaption></figure>

1. **`Branch Name:`** Name of the branch assigned.
2. **`Branch Settings:`**&#x54;his option allows you to update your branch configuration, which means:

   * you can add your branch to one of the standard branch types *(development, integration, quality assurance, production, etc.)*
   * configure your parent branch
   * update the metadata folder path and/or,
   * update the branch's last commit date.

   **Pieces of information related to 'Metadata Folder Path'**

   * When the user changes the **`Metadata Folder Path`**, ARM updates the **project-def.json** file at the time of the initial commit. The commits will now occur in the newly created *.src* folder once the src metadata folder location has been updated. In an instance where the user has many commits on the newly created src folder and then reverts the src folder to default, all of the components in the src folder will now be included in the **package.xml** as well.

<figure><img src="/files/bIqNfBsLdIk4io7nYm4G" alt="" width="375"><figcaption></figcaption></figure>

1. **`Smart Commits-Sync:`** Use this toggle button to start/stop syncing external [Smart Commits](/product-guides/arm/arm-administration/alm-management.md). If you try to sync external commits to a branch that has not been mapped, you will see a notification popup. You must map the required branch under **`Admin > ALM Mgmt > Repository Mappings`**, then you can proceed to sync the external smart commits. For more information on mapping a branch, refer [HERE](/product-guides/arm/arm-administration/alm-management.md).

<figure><img src="/files/SuMsyinuGbmWUGE2yY70" alt=""><figcaption></figcaption></figure>

4. **`Status:`** View the branch status along with the branch log report.
5. **`Info:`** Hover your mouse over the icon to view the branch details, such as the branch created date, parent branch, and author details.

<figure><img src="/files/04pweTUzB7EBwFGJy52S" alt=""><figcaption></figcaption></figure>

6. **`Clear AutorabitExtId:`** Deletes the **`AutorabitExtId__c`** field from your branch.
7. **`Migrate:`** Migrates custom object field **`Picklist`** to **`Value Set`** in your branch.

### FAQ

### Is it feasible to update the repository URL without having to re-register the repository in ARM? <a href="#is-it-feasible-to-update-the-repository-url-without-having-to-reregister-the-repository-in-arm" id="is-it-feasible-to-update-the-repository-url-without-having-to-reregister-the-repository-in-arm"></a>

The repository URL cannot be changed; you must use the new repository URL and re-register it with ARM. To register a new repository, click this [link](/product-guides/arm/arm-features/version-control/introduction-to-version-control/version-control-repositories-summary.md).

### Why am I getting an error while registering the GitHub repository with SSH? <a href="#why-am-i-getting-an-error-while-trying-to-register-github-repository-with-ssh" id="why-am-i-getting-an-error-while-trying-to-register-github-repository-with-ssh"></a>

**GitHub** no longer allows new **RSA** keys with **SHA-1** signatures. Execute the `ssh-keygen -t ed25519 -C “sampath.c@autorabit.com”` command in the terminal to create a new key, or contact **<support@autorabit.com>** for further assistance. Please note that you must create the new key in **Linux** or **Unix**, not in Windows. For more information, visit <https://github.blog/2021-09-01-improving-git-protocol-security-github/>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://knowledgebase.autorabit.com/product-guides/arm/arm-features/version-control/introduction-to-version-control/version-control-repositories-summary.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.