Checkout files
You can checkout a project from the SCM menu or directly from the location of your new working directory.
Add files
Complete this procedure to add unversioned files found in the checkout directory.
Commit / Review changes
To commit your updated version of a file to the repository, right-click on the file in your Project and choose SCM >> Review Changes.
Locking Locking a file provides exclusive rights to a user for changing that file in the repository. As long as the file in the repository is locked by a user, no other user can change (commit) that file in the repository. This helps to avoid conflicting commits.
Revert changes / Un-add files
You can discard changes to files not yet committed, and you can unadd files which have been added but not yet committed.
Delete files
The Delete command deletes a file from your checkout directory and from the repository.
Update / Update All Update / Update All updates any outdated files in your project with the latest version stored in the repository.
Cleanup The Cleanup command cleans up the working copy, removing stale locks.
Copy working files and directories
A Subversion working copy is an ordinary directory tree on your local system, containing a collection of files. You can create another copy of your project, project files, or directories, to allow parallel development, for example.
Merge and revert
Follow this procedure to merge and revert changes from a range of revisions.
Move a working copy (Switch)
The Switch subcommand allows you to move a working copy to a new branch of the repository.
Create patch
You can create a patch file containing the differences between your working copies and the corresponding files in the repository. The created file is in Unidiff format.
Apply patch The Apply patch command applies a patch file to files in the repository.
Browse repository
The SVN Repository lists the files in your selected repository and branch.
Integrate bug tracking
Changes made in your project may also be related to a specific bug or issue ID. If you use a bug tracking system (such as Bugzilla) you can associate the changes you make in your Source Code Management system (such as Subversion) to its bug tracking ID.