Over a million developers have joined DZone.

Checking Your Changes with SVN

· DevOps Zone

The DevOps zone is brought to you in partnership with Sonatype Nexus. The Nexus suite helps scale your DevOps delivery with continuous component intelligence integrated into development tools, including Eclipse, IntelliJ, Jenkins, Bamboo, SonarQube and more. Schedule a demo today

Before committing work to the central repository, you may want to review the changes you’ve made. This can be achieved by running Apache Subversion’s ‘svn status’ command at the top of your working copy, which will print out a list of all your local changes:

svn status (working-copy-path)

svn status

The characters in the first column represent the state of the file/directory listed. The different characters are:

  • ? – item is not under version control.
  • ! – item is missing.
  • A – item is scheduled to be added to the repository.
  • C – item is in a state of conflict.
  • D – item is scheduled to be deleted in the repository.
  • M – item contents have been modified.

Alternatively, if you need information about all the files in your working copy, regardless of whether they have been modified, you can add Subversion’s –verbose (–v) switch to ‘svn status:’

svn status –v (working-copy-path)

svn status 2

The DevOps zone is brought to you in partnership with Sonatype Nexus. Use the Nexus Suite to automate your software supply chain and ensure you're using the highest quality open source components at every step of the development lifecycle. Get Nexus today


Published at DZone with permission of Jessica Thornsby, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

The best of DZone straight to your inbox.

Please provide a valid email address.

Thanks for subscribing!

Awesome! Check your inbox to verify your email so you can start receiving the latest in tech news and resources.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}