Aaron Brazell

Whenever you make an SVN commit on a <a href="http://code.google.com" rel="nofollow ugc">Google Code</a> project, you can instruct Google to send a notice to someplace else. Utilizing the upcoming custom post type functionality in WordPress 3.0, this plugin creates a new content type called SVN and inserts the post commit messages from Google Code into WordPress.
This plugin serves as a functional example of how custom post types are supposed to work. At the time of this release, WordPress 3.0 is not out and thus not officially supported in word or implication. Do not ask me to support custom content types. 🙂
Also, because WordPress 3.0 is pre-release, the functionality might (but probably won’t) change. I’ll do my best to keep this up to date.
Note, you must have WordPress 3.0 (pre-release) and PHP 5.2+
<h3>Arbitrary</h3>
Someone asked me what my favorite thing is? Battle unicorns. That is all… carry on.

Google Code Commit Tracking

Logs Google Code subversion post commit messages into WordPress.

Adam Harley (Kawauso)

Checks for the presence of the <code>.svn</code> directory in each plugin’s directory. Disabled for plugins with their files directly in the <code>/plugins/</code> directory to prevent false positives.
Also supports other systems through the use of the <code>REVISION_CONTROL</code> constant. Just set this to the directory created by your revision control system in your <code>wp-config.php</code>
Based on <a href="http://developersmind.com/2010/06/12/preventing-wordpress-from-checking-for-updates-for-a-plugin/" rel="nofollow ugc">code</a> by PeteMall.

No Updates for Plugins under Revision Control

Prevents plugins from being updated by the WordPress updater if they are under Subversion revision control (or other systems).

Google Code Commit Tracking vs No Updates for Plugins under Revision Control