1. Update your working copy – When you resume work on a project, the first thing you should do is make sure you have the latest version by using the update command to download everyone else's changes.
2. Make your changes to the project – In addition to changing the contents of files, you might add, delete, copy, or move files and/or directories. Be aware that many clients will require you to specifically add new files/directories to version control.
3. Examine your changes – Using combinations of the status, diff, and revert commands you can review or backout any changes you have made.
4. Update your working copy and Merge other changes into your working copy – Before committing your changes, you will need to make sure you merge those changes with any changes other developers have made. First update your working copy. Your client will alert you to any conflicts that might exist and prompt you to merge those changes.
5. Commit your changes – Lastly, you want to commit you changes to the repository. You should commit frequently to preserve your work. However, you should also try to commit only working code (so no one else has to suffer through your bugs). Also, you should commit sets of changes that generally go together to add some new feature or fix a bug.

    

Learn More!

• ASU Web Developer Community website - A place where all ASU Web Developers can go to collaborate on projects and share ideas. This site also houses the top level administrative interface to the Subversion system. If you don't find what you are looking for, use one of the other resources listed below or ask in the Forums. Once you find an answer, please consider writing an article. Click "Create Content - Article". Choose a title, tag the article with the appropriate topics, write and submit. If you're too shy to submit your work for immediate publication, simply email it to one of the site administrators (Jeff Beeman, Kelli Thornoton, Adrian Teo, or me) and we'll help you get it in shape and post it.
• Community Forums - Have a specific question? Debating on the various ways to organize your project? Not sure how to setup workflow within your group? The forums on the Community site are a great resource to connect with and learn from fellow developers at ASU.
• How to use Subversion - The official documentation for Subversion in the free, online Subversion Book.
• Pragmatic Version Control using Subversion - An excellent guide to Source Code Management best practices with a focus on Subversion.

Want to help improve the service?

Contact the Subversion administration team at subversion.request@asu.edu. Let us know about any ideas you have that could make this service more useful to you or other developers. Some things we're thinking about are: an online diff viewer like ViewVC, integration with bug tracking systems, searchable log messages, and automated code validation.