Committing Your Code

• Changelogic
• Getting Started
• Commit To Change

Why commit?
Committing means sending your locally made edits to the central VCS server. This serves as a back-up; also, you may continue working on the same change elsewhere simply by starting development there.

To commit your edits to the VCS, run ant commit from command line. Upon this command Changelogic checks whether your change is still being developed, and then commits the main repository and all editable modules.

Unlike in traditional VCSs, in Changelogic you may commit safely at any time without fearing that some broken code would block other developers and drive them mad. The changes are isolated and your code does not reach others until the code gets integrated.
NOTE: changes shared with other developers are an exception here.

A commit is automatically performed first when you are ending development, uploading diff or starting base version update. Be sure to commit before switching changes unless you want your uncommitted edits to be transferred into the other change.

NOTE: we do not advise using your VCS client to commit your files as using it has occasionally caused committing into wrong change. Also, in a project with complex module structure, the VCS client would have to be acknowledged of every editable module. See our FAQ for information on what CVS operations you can do manually.