Track Traffic to GitHub Repo for More Than 14 Days

You should be able to just pull down the other repo and have it merge with yours.

git pull {url-of-repo-with-commit-you-want-to-merge-in}

This will fetch the repo mentioned and have it automatically fast forward merge in any commits you don't have into yours.

So in your example, while on your master branch, or if you want to test it out on some other branch:

git pull git://github.com/dantipa/history.js.git
remote: Counting objects: 9, done.
remote: Compressing objects: 100% (1/1), done.
remote: Total 5 (delta 4), reused 5 (delta 4)
Unpacking objects: 100% (5/5), done.
From git://github.com/dantipa/history.js
 * branch            HEAD       -> FETCH_HEAD
Updating e84ad00..e2d5251
Fast-forward
 scripts/uncompressed/history.js |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

Now with the other commit merged with yours you can push back up to your own remote with that extra change.

There is an Issues API. To get all issues from a repo, you can use cURL:

curl -i https://api.github.com/repos/username/reponame/issues

This returns a JSON encoded list of all issues. And …

curl -i https://api.github.com/repos/username/reponame/issues?status=open

… returns all open issues. Now you just have to convert the JSON to CSV and you are set.