You are here:
Version Control System Synchronization
Maintain consistency between your pipeline and your source control repository by detecting external changes and merges.
Required Editions
| Available in: Lightning Experience in Professional (API access required), Enterprise, Performance, Unlimited, and Developer Editions |
| Available in: Government Cloud Plus as interoperable. Turning on DevOps Center in Government Cloud Plus orgs can send data outside the authorization boundary. Contact your Salesforce account executive for more details. |
| Not available in: EU Operating Zone. EU Operating zone is a special paid offering that provides an enhanced level of data residency commitment. DevOps Center is supported in orgs in the EU that aren’t part of EU OZ, per standard product terms and conditions. |
The Version Control System (VCS) synchronization process maintains the version control system as the single source of truth for your work items, minimizing merge conflicts and environment inconsistencies. It makes sure that all changes, whether merged or committed directly to the source control repository, or performed using Git CLI tools, remain consistent with DevOps Center.
With VCS synchronization, developers can continue to manage branches and change requests using external tools, such as Git CLI or the source control provider’s UI. Meanwhile, deployment managers and DevOps Center admins maintain full visibility of those changes within the DevOps Center pipeline.
DevOps Center automatically runs VCS synchronization during user actions, such as promoting changes or viewing a work item. When you promote work items, DevOps Center checks the pipeline for external merges (changes made directly to the source control repository). In case of an external merge, DevOps Center analyzes the changes and updates the pipeline and work items with the latest changes.
DevOps Center detects specific events in the source control repository and maps them to DevOps Center actions.
| VCS Event | DevOps Center Action |
|---|---|
| Create a work item branch. | Maps the branch name to a work item and sets it as the development branch. |
| Open a change request (PR) | Updates the status of the corresponding work item or stage to indicate that a review is in progress. |
| Approve a change request. | Marks the associated work item as Approved or Ready to Promote. |
| Merge from work item to stage. | Validates the merge sequence and tracks the merge. |
| Merge from stage to stage. | Verifies that the source and target branches represent consecutive stages in the pipeline. |
