@ghuser/github-contribs

github-contribs

List all GitHub repos a user has contributed to since the beginning of time:

• not just the last few months,
• not just the repos owned by the user or their organisations,
• simply all repos a user has ever pushed to.

$ github-contribs AurelienLourot
✔ Fetched first day at GitHub: 2015-04-04.
⚠ Be patient. The whole process might take up to an hour... Consider using --since and/or --until
✔ Fetched all commits and PRs.
35 repo(s) found:
AurelienLourot/lsankidb
reframejs/reframe
dracula/gitk
...

⇒ Advanced usage

Installation

$ sudo npm install -g @ghuser/github-contribs

Contributing

To run your local changes:

$ yarn install
$ ./cli.js --help

Team

This project is maintained by the following person(s) and a bunch of awesome contributors.

Aurelien Lourot

FAQ

How does it work?

Normally in order to retrieve all repositories a user has interacted with, one should query the GitHub Events API. Unfortunately it returns only the last 90 days, so we don't use it.

Instead we noticed that the "Contribution Activity" on the profile pages queries such URLs in the background:

• https://github.com/users/AurelienLourot/created_commits?from=2018-05-17&to=2018-05-17
• https://github.com/users/AurelienLourot/created_repositories?from=2018-05-17&to=2018-05-17
• https://github.com/users/AurelienLourot/created_pull_requests?from=2018-05-17&to=2018-05-17
• https://github.com/users/AurelienLourot/created_pull_request_reviews?from=2018-05-17&to=2018-05-17

So we're doing the same :)

Why is it so slow?

We hit a rate limit. And since it's not an official API, we can't use a token to raise the limit.

Isn't it likely to break?

Yes, it is since that interface isn't public. We're monitoring it and will react as fast as we can when it breaks.

Changelog

2.0.0 (2018-06-25):

• Exported some helper functions.

1.0.0 (2018-06-11):

• Support for passing a GitHub API key.

0.0.2 (2018-05-29):

• Cosmetic improvements to the npm page.

0.0.1 (2018-05-29):

• Initial version.

Similar/Related projects

• GitHub-contributions: uses a different technique. It fetches all the user's pull requests from the official API. This is clever but will miss the repos to which the user has pushed directly without pull request.
• gharchive.org: records all GitHub events for all users. In theory it should be possible to replace our implementation by queries to this huge database.