Alan Gutierrez compares Sourceforge and Github. In short: Sourceforge is for projects, while Github is a place to put your code. It doesn’t have to be a full project. It doesn’t have to work. It’s just a way to share your code with other hackers who might be interested. And they can fork it and start collaborating.

My new favorite git command:

$ git reset --soft HEAD^

This pulls out your most recent commit, putting the changes back into your working tree. It’s exactly like an undo button for whatever you just committed.

Rebase is one of Git’s most alluring and yet most difficult-to-comprehend features. Rebasing is editing commits. When you rebase, you’re rewriting history.

Git submodules are pretty cool, except for kind of sucking. Things I don’t recommend doing if you value your sanity:

In the spirit of Graeme Mathieson’s git techniques, here are a few of my favorites, with their svn equivalents for reference.

It tickles me to death that Git highlights loose whitespace in red.

git-wiki is a wiki written in less than 200 lines of code using Sinatra as the web framework and Git as the database. Quite clever. Check out how they store the CSS at the end of the file using __END__ - a Ruby trick I was previously unawrae of.

It seems that Git fever is going around.

For a while, everything that we did in Heroku to extend the functionality of Rails, or interoperate with it, has been done through extension mechanisms. Monkeypatching via plugins, use of the somewhat obscure Mongrel GemPlugin, and tweaking of the user’s Rails app files directly. (We try to avoid that last one whenever possible. Early on we did a lot of it, but more recently we’ve managed to avoid it almost entirely, much to my relief.)

I’ve been sold on the concept of distributed revision control systems ever since Simon Michael showed me Darcs a year ago. But I’ve been slow to adopt it for any real use. Part of the reason for this was that I wasn’t super-happy with the implementations available, although there are quite a few. Darcs certainly seemed like the best of the bunch, but it never felt quite right to me. Besides being sluggish, it relies on tons of interactive prompting - which is not the sort of UX I look for in a command-line tool.