What is source code versioning in Salesforce?

Hi,

environments. The repository, such as Git or Apache Subversion (SVN), helps integrate the changes that were implemented by concurrent development and separates the different versions of an application.

The source control repository contains a copy of your entire organization’s metadata as exposed by Metadata API. Team members can add their customizations, such as custom objects,  fields, and reports, and Apex or Visualforce code to the source control repository. These changes are then merged with changes that were made by other team members or developers on other teams. A source control system ensures a quality development process and has many other benefits, including the ability to deploy only a specific version of customizations, and maintaining a separate branch for each project without overwriting customization done as part of other projects.

In the source control system that you use, such as Git, you can create a repository with multiple branches. Each branch contains a set of changes that are developed by a separate team. For example, one team of developers might be working on a feature that’s going live in February.  Another team might be working on a feature that’s going live in March.  These teams need separate Developer organizations and integration test sandboxes.  In addition, because patch releases contain bug fixes and therefore different customization metadata and Apex code than new features, use a separate branch for a patch release.

You can use the Ant Migration Tool to retrieve a copy of your organization’s metadata to commit to source control. Conversely, the Ant Migration Tool can be used to deploy metadata that’s saved in source control to an organization.
Hope this helps.