Version Control Repositories Summary

Important Note: This article is for the Org Administrator in particular. The actions discussed in the article will not be available to general users.

Overview

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 icon displayed, and nCino objects configured will have icon beside their repository under Repositories List for easier identification.

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.

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.

Pull Request Support

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.

Pull requests can only be opened between two branches that are different. More detailed instructions are available in a separate article; please refer HERE.

Branches/Tags

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.

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)

B. Register a Branch

Register an existing branch to the current repository. (LEARN MORE)

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.

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:

1. Branch Name: Name of the branch assigned.

2. Branch Settings:This 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'

   • The default metadata folder path is in the following format: force-app/main/default

   • 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 the 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.

   • For ARM to detect your repository as being in DX format, it looks for an sfdx-project.json file in your local directory. The sfdx-project.json file is the configuration file. For the SFDX repository created outside and registered later with ARM, the source folder has to be declared in the sfdx-project.json file under the array named packageDirectories. This will allow you to pick the source folder you declared in the sfdx-project.json during the commit/ CI Job operation or while creating unlocked packages.

   • The folder name must be entered in the Metadata Folder Path field for SFDX repositories where foldername/force-app/main/default/ counts as the metadata folder path.

   
3. Smart Commits-Sync: Use this toggle button to start/stop syncing external Smart Commits. 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.

   
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.

1. Clear AutorabitExtId: Deletes the AutorabitExtId__c field from your branch.

2. Migrate: Migrates custom object field Picklist to Value Set in your branch.