on-the-githubs



Demo: http://kvz.github.io/on-the-githubs/#repos/kvz/nsfailover

To grow an open-source community it helps if your site has an active overview of what's going on and who
is contributing.

The GitHub API3 provides all the information we need, but you may hit rate-limiters, or find it hard / have no time to embed this data into your website.

This project aims to make it deadsimple to add community info & activity feeds to your project's site.

On the Githubs example

On the Githubs is a jquery plugin for a near-realtime overview of activity of a user, project or organisation.
It does not require any buildsteps or setup, just add a few lines of code to your project's HTML.

Demo: http://kvz.github.io/on-the-githubs/#repos/kvz/nsfailover

Or your own:

- http://kvz.github.io/on-the-githubs/#repos/{user}/{repo}
- http://kvz.github.io/on-the-githubs/#users/{user}
- http://kvz.github.io/on-the-githubs/#orgs/{org}

To embed this into your site, add a few lines of code:

``html



`

Don't forget to change the data-event-source to repos/{user}/{repo}.

On the Githubs development

For local development, here's how to run the repo-included demo:

`bash
npm install --dev
make build
node demo-server.js
`

- Point your browser to http://127.0.0.1:8080

Bonus: In the Githubs

Activity is limited to the last 20-100 events, but communities grow big.
If you want to give credit where credit is due and show all the faces that make your community,
we can't just pull that in in realtime from the API without hindering the UI or hitting GitHub's
rate-limiter.

So this is something we have to aggregate, cache, and compile at your site's buildtime.

In the Githubs examples

Get all people involved with kvz/nsfailver and echo as json to stdout

`bash
./bin/in-the-githubs --user kvz --repo nsfailover --format json --output -
`

Index an entire organization, read test/about.md, search it for the {{community}} tag,
replace it with the entire tus community, write it to test/about-with-community.md, do this with 1 request at a time, to ensure the order of userpaths. Enable debugging to see what's going on, because with the amount of API requests & GitHubs rate-limiting, this is going to take a while (the script automatically waits as to not have your IP banned by GitHub).

`bash
./bin/in-the-githubs \
--user tus \
--repo tus.io,tusd,tus-jquery-client,tus-ios-client,tus-android-client,tus-resumable-upload-protocol \
--format html \
--concurrency 1 \
--input demo.html \
--tag '