Book a Demo
Prev Next

Resynchronize the Status of Version Controlled Packages

It is possible to update the Version Control status of Packages within your project to re-synchronize with the status reported by your Version Control provider. This can be useful if you are creating copies of your project, where checking in a Package from one copy of the model leaves the Package in the second copy of the model with an out-of-date Version Control status.

For a given Package, the re-synchronization process queries the corresponding Version Control provider to find the status of the Package file associated with the Version Controlled Package. If necessary, the process then updates the Package flags within the model database, to synchronize the Package status recorded in the model with the value reported by the Version Control provider.



Settings > Version Control > Re-Synch Status (applies to all Packages in model)

Context Menu

Right-click on Package > Package Control > Re-synch Status With VC Provider (applies to single Package only)

Resynchronize Version Control status



See also


The results of the re-synchronization process are sent to the System Output window.

The System Output Window


Double-click on any result message to select, in the Browser window, the corresponding Package.


  • This process does not cause any Package data to be either exported from your model to the associated Package file, or imported from a Package file into your model's Package data
  • If a Package has been checked-out and modified with Enterprise Architect, but your Version Control provider reports the Package file as checked-in, running this process marks the Package within Enterprise Architect as being checked-in, without exporting and committing the pending changes; subsequently checking-out the Package imports the latest revision of the Package file from Version Control, effectively discarding the uncommitted modifications from the model
  • Similarly, if a Package file is checked-out to you in your local working copy folder, but not in the Enterprise Architect model, running this process marks the Package within the model as checked-out, but it does not import the associated Package file from the Version Control system; consequently, it is possible to check-in a Package from Enterprise Architect that is potentially out of date, compared to the latest revision of the Package file within the Version Control system