Add to Subversion

I love Rails generators and I love Subversion, but I'm not so sure they love each other.

Little is worse than generating some scaffold files or a login system, tediously typing svn add ... a bunch of times, and later learning that you missed a file. Oops.

Given that, here's my hack to get the Rails generators and Subversion to kiss and make up:

desc "Add generated files to Subversion"
task :add_to_svn do
  sh %Q{svn status | ruby -nae 'system "svn add \#{$F[1]}" if $F[0] == "?"'}
end

I put that in "lib/tasks/add_to_svn.rake" for all my Rails projects. You can then access it whenever you need with rake add_to_svn.

I've seen similar tasks posted, but they've always been Unix specific and I work with some Windows programmers. This is my attempt to help both on platforms.

How does it work?

You're probably not use to seeing ugly Ruby code like that, but Ruby supports a lot of command-line shortcuts it inherited from Perl. Here's a breakdown of the options used:

-e The code to execute directly follows this option.
-n Wrap my code in a standard Unix filter style processing loop.
-a Auto-split each line of input.

Together they mean that Ruby sees the above input as something close to:

ARGF.each_line do |line|
  $F = line.split

  # my custom code is inserted here...
  system "svn add #{$F[1]}" if $F[0] == "?"
end

That just asks Ruby to call svn add ... for each file svn status flagged with a "?". Those will be all the files Subversion doesn't yet recognize.

WARNING: Make sure you've told Subversion to ignore files you don't want it messing with (like Rails's log files), or they will be added!

% ruby script/generate | grep -- -c
-c, --svn                        Modify files with subversion. (Note: svn must be in path)

Add Your Thoughts

You can use Markdown in the body of your comment to format text and make links.

Note that I reserve the right to edit any content you post here. I typically exercise this right to fix formatting issues. All posts must be approved so spam will never been seen on these pages.

Author:

URL or Email (optional):

Body: