Commiting to SVN 

The commit process is initiated via the SVN > Commit menu option. This command commits the changes in your local working copy to the repository.

 To commit a resource to SVN repository

  1. Right-click (Mac OS: Ctrl+click) the model item (the item of the uppermost level) in the Projects tree and choose SVN >  Commit... from the popup menu, or
    Select any element of the model and choose File > SVN >  Commit... from the main menu.
  2. If there were no changes made since the last commit operation, you will see the dialog with the corresponding message shown:

  1. Otherwise, you will see the Commit dialog.

  1. Enter a comment to associate with the commit or choose a previously entered comment from the list. 
  2. In the Changes field you should specify which particular changes you want to commit to SVN repository. The scope of the commit operation is relative to the resource(s) you have selected, and will list modified, added, deleted and unknown resources. All modified, added and deleted resources will be selected by default.
    You select/deselect a resource by ticking on/off checkboxes to the left of its tree item. To select all resources, right-click (Mac OS: Ctrl+click) in the empty area of the Changes field and choose Select All from the popup menu. Conversely, to deselect all resources, click Deselect All.

In the Changes tree, resources may have specific icon modifiers that may help you:

Icon modifier

Description

The resource was added locally.

The resource was modified locally.

Conflicting resources. The local and incoming verisions of the resource are conflicting.

The resource was deleted locally.

  1. When finished, click OK to commit the selected changes to the SVN repository.

If the commit was successful, you should see that the information in the model tag (the revision number and the timestamp) was updated:

Your working copy must be up-to-date with respect to the resources you are committing. This is ensured by using SVN > Update, just prior to committing, resolving conflicts and re-testing as needed, as described in the typical work cycle