> I disagree. Finding your way around a foreign code base enough to make the changes you need is an essential skill for a developer.
Sure, but a whole lot of the forks are like one line changes, they sit there taking up an entire repo, and aren't particularly useful.
You should use your user page[1] to draw attention to the things you think are most important.
> Additionally, if I fork a project, it's likely just so that I can add a fix and issue a pull request, that's additionally something I don't think people need to see.
I disagree. Finding your way around a foreign code base enough to make the changes you need is an essential skill for a developer. Repositories you've forked and made pull requests for are a great way to demonstrate that.
[1]: http://help.github.com/pages/