Added include_forks path parameter

[newracket]

I modified the code slightly so now the isFork argument in the API request is variable. I added an include_forks path parameter, and if it's true, it passes in isFork: null, in which the API sends all repos, whether they're forks or not. And if the include_forks path parameter is missing, or is any value other than true, it passes in isFork: false, which is the current behavior.

Note: I've read the other posts, along with the comment at #1122 (comment). I understand that point of view, but I think adding include_forks would be beneficial. For example:

I've worked on a few projects with a small number of contributors, but I don't own those repositories, so I need to make a fork for it to appear on my profile. I'd like those projects to appear under my top-langs image, so allowing forks would let me do that. And to address the comment I linked above, I use the exclude_repo parameter to exclude my forks with a large number of contributors.

Suggestion? (A possible alternate solution could be to change include_forks to be like exclude_forks, where instead of passing in true or false, you pass in a list of forked repository names to include?).

[vercel]

@newracket is attempting to deploy a commit to the github readme stats Team on Vercel.

A member of the Team first needs to authorize it.