Committing Changes

Stores your changes back in the repository

then others can update their working areas and get your changes

When should you commit?

When you've completed a set of consistent changes
After you've unit-tested them reasonably
When it's time for other people to be able to see them

(Also called "checking in" files)