Rspec is still at 53%, with votes as of 1/13/09

D2h mentioned in a talk a while ago that the idea is to give Rails users a sane default test framework that is as simple as possible.

Isn’t that cucumber / rspec?

Now, admittedly the people responding to that pole are probably more likely to be rspec users than the average rails coder, but rspec more than twice as popular as test/unit.

I think I even remember seeing some 37signals snippet of a campfire chat, where they were talking about rake spec passing.

So, you want to see your repository in a brand new way. You’re sick of the command line, you need to see some graphs! Pixels! Buttons! Graphics! Dialog boxes! Ok, we get the point.

Our first option is viewing your repo in a browser. This functionality is packaged with most git installs:

git instaweb

This will fire up a server, usually lighttpd, to serve a simple web interface for your repository. You can browse commits, trees, view files, what have you.

To complement David’s earlier announcement regarding Passenger support in the Brightbox gem we’re also launching a very special discount offer for the rest of January 2009…

You just committed that awesome feature/test/bug, but something just isn’t right. Either some information isn’t filled out, the commit message is wrong, or something else is just messed up. Let’s go over what can be done to fix the associated data after the fact.

Fixing the previous commit is very simple. Just use

git commit --amend

And that will fire up the commit patch in $EDITOR for you to mess with. Simply edit the message right on the top line of the file, save, quit and you’re done.