Using version control for your orgs requires some initial setup. To set up version control:

1. Make sure the org where your source of truth data resides is the org where you have installed the Prodly managed package (your control org).
2. Release uses a single repository in your version control system (VCS) to track and manage changes you make to the data in all the orgs you place under version control. Prodly recommends starting with an empty repository containing only the default main branch. Our current release integrates with Azure Cloud, Bitbucket Cloud, GitHub Cloud, GitLab Cloud and several flavors of GitHub Enterprise Server. Refer to the Azure, Bitbucket, GitHub or GitLab documentation to correctly configure the VCS environment (access permissions, etc.) for your use case. For assistance creating a repository, refer to the related Azure, Bitbucket, GitHub or GitLab  help topic.
3. From the Settings page, click the General Settings tab.
4. Click Set Up Integration to launch the VCS setup wizard.
5. On the Connect page of the wizard, you connect Release to your VCS repository.
   1. In the Version Control System list, select the version control system to use for data storage and management.
   2. If Azure Cloud is not in the list:
      1. In the Salesforce org where you installed the Prodly managed package, navigate to Setup > Object Manager > VCS Repo > Fields & Relationships > Repo Type.
      2. Scroll down to the Values section and click New.
      3. Enter Azure Repo.
      4. Click Save.
   3. Specify the parameters Release needs to access your VCS account:
      • For Bitbucket Cloud:
        1. In the Workspace box, enter your Bitbucket account workspace.​
        2. Notice Release automatically sets Base URL to bitbucket.org.​
      • For GitHub Cloud:
        1. Select an Authentication Method.
        2. When Authentication Method is Personal Access Token, in the Personal Access Token box, enter the GitHub personal access token for your VCS account.
        3. For either authentication method, in the Base URL box, enter web address of your VCS account.
      • For GitHub Enterprise Server:
        1. In the Personal Access Token box, enter the GitHub personal access token for your VCS account.
        2. In the Base URL box, enter web address of your VCS account.​
      • For Azure Cloud:
        1. In the Personal Access Token box, enter the Azure personal access token for your VCS account.
        2. In the Project URL box, enter the web address of the Azure project in your VCS to use.
      • For GitLab Cloud:
        1. Select an Authentication Method.
        2. When Authentication Method is Personal Access Token, in the Personal Access Token box, enter the GitLab personal access token for your VCS account.
        3. For either authentication method, in the Base URL box, enter web address of your VCS account.
   4. Click Connect.
   5. Follow the VCS prompts to establish a connection between Release and your VCS for your Salesforce user.
   6. In the Repository list retrieved from the VCS, select the repository to use for version control.
   7. In the Branch list retrieved from the VCS, select the branch to use for version control.
   8. Choose if you wish to specify a Folder for your commits to be allocated to within your branch.
   9. Enter a required Commit Message
   10. Click Continue.
6. On the Configure page of the wizard, you select the Salesforce objects to place under version control.
   1. Select the Schema org you wish to reference for Version Control data.
   2. In the Available Objects select the objects to place under version control. Release tracks all fields in and relationships between the objects you select.
   3. Click Continue.

7. On the Commit page of the wizard, you confirm and initiate saving the initial source of truth data to the branch of the VCS repository you specified.
   1. Review the Objects list to ensure you have chosen your desired objects.
   2. Click Save.

When initialization completes, your VCS repository information appears in the Version Control Integration table.

And under the Release tab, the Branch: line appears on the control org card.