Refresh Model

Refresh Model

This action updates the local copy of a model by importing and merging all changes that have been published to the remote model by other collaborators. You need to ensure that a remote repository has been configured first. See Configuring a Remote Repository for more details.

Technically the Refresh process corresponds to Git "fetch" and "merge" operations.

The action is enabled when a model that is configured for collaboration has the focus.

If you have uncommitted or unsaved changes in your local model you will need to commit these changes first.

The action performs these steps:

1. Checks that a remote repository has been set
2. Checks whether the model needs saving
3. Checks if there are uncommitted changes
4. Asks for a user name and password if the online repository is configured as HTTPS and these credentials are not stored
5. Fetches updates from the remote server and updates new branches and tags
6. If there are changes for the current branch, attempts to merge the remote changes for the current branch with the local model. There may be conflicting changes which will have to be resolved.

Merging and conflicts

Important

Merging and conflict handling is a work in progress. A merge may not be successful in which case you will have to choose between "Mine" and "Theirs".