Synchronizing with the repositoryWorking with shared resources requires tracking their state in context of
the repository content. This could be done by creating a synchronization that populates the Synchronize view and
benefiting following advantages:
- The local modification state of the resources being synchronized is kept up-to-date. This means that, if you
modify a file locally that is within the scope of a synchronization that appears in the Synchronize view, the
resource will appear automatically in the view, if it is not already there.
- The remote state of all of the resources being synchronized can be refreshed using the Synchronize button in the toolbar of the Synchronize view.
- The remote state of a selection of resources can be refreshed using the Synchronize command from the context
menu in the Synchronize view.
Following methods can be used to create a synchronization.
Method 1: Using the context menu
To synchronize resources in the Workbench with those in the repository:
- In one of the navigation views, select the resources that you want to synchronize.
- Right click and select Team > Synchronize with Repository. The Synchronize view opens.
Method 2: Using the synchronize action
- From the Team Synchronizing perspective select the Synchronize... action from the Synchronize
button drop down.
- Select your VSC type from the list of possible synchronization types and click
Note: If there are no other repository providers registered with the Workbench, then you will bypass this
- Select the resource scope for the synchronize by either selecting Workspace, Selected Resources or Working Set.
Then select Finish.
- The Synchronize view will open.
Note: The synchronize action is not enabled by default in other perspectives. You can enable the action
to appear in your current perspective by selecting Window > Perspective > Customize
Perspective. Then click on the Commands tab and check off Team.
Note: It is possible that someone has committed a new revision of your file since you started working on
it. This will result in a conflict, and care must be taken to resolve this. For this reason, conflicts are
shown in all modes of the Synchronize view.
Important: It is preferable to update resources in the Workbench first, resolve any conflicts that exist
by merging, then commit Workbench resources to the repository.
Three way comparisons
Merging changes in the Compare editor
Version control life cycle: adding and ignoring resources