You can use the confirmation dialog to compare your new version with any past version and to make any necessary edits in the current version. Any changes you make as you review a file are included in the committed file and saved in your project.

If you’re using Subversion, a commit operation copies the changes from selected files into the remote Subversion repository. Therefore, you must be connected to the repository before you can commit changes. (For details, see your repository administrator.)

If you’re using Git, the commit operation adds your changes to your local working copy. If you're using a remote Git repository, you have to perform a push operation to add your committed changes to the shared repository.

A commit comment is required; the Commit button is disabled until you enter one. Good comments are specific, but concise; suggested content includes a brief description of the changes, what they are meant to accomplish, and URLs or ID numbers of any relevant bugs. The version editor displays the affected code together with your name and commit comment, so you can omit information that’s in code comments or that’s obvious from looking at the line of code.