Generate team and contributors for homepage automatically from GitHub.

[bmpvieira]

The layout is already generated from a JSON downloaded from GitHub, so it should be just a matter of making query automatically GitHub API.

[thejmazz]

I can try to set this up. Looks like _data.json is the file in question? How did you get core and members from the GitHub API? I'm assuming you just saved a GitHub API response? There's private members on the website we'll probably have to auth the GitHub API requests to get those.

I've found

• orgs/bionode
• orgs/bionode/members
• orgs/bionode/public_members

Appending /orgs/bionode/members?access_token=ACCESS_TOKEN, returns private and public members, but I still don't see how you are programmatically separating core and members.

I seem to remember there was a core team from my brief time as an admin ;)

So, maybe you need to be admin to get that info, and its two teams.

In any case, a curl https://api.github.com/api_url?access_token=$ACCESS_TOKEN > _data.json as a package.json script was what I was thinking for this.

Instead of making an environment variable for the token, committing a token that only has read:org permissions should be safe. But then anyone can see private members...which is the case on the website anyways..

[bmpvieira]

Thanks for giving a shot at this. I've made both core and contributors public, does it help?

[thejmazz]

It does - though maybe you didn't need to? I didn't try /org/bionode/teams before lol. (see PS)

Here's my testing with curl - I'll commit these into an npm run gen-members later..

First, with no auth, on endpoint orgs/bionode/teams:

Then with my access token with read:org permissions (as an env. var.):

Then copy/pasting the members_url and removing the {/member} (can obviously automate this easily):

Will have to remove dupes, but thats easy.

Would be fun to do this in pure bash lol, but I'll do it up in JS for cross-platform compatibility and so its more readable than a bunch of curl url | grep login | cut -d':' -f2s lol. I'll add instructions to the readme how to use the script too. Expect a PR in the next few days..

PS. The teams are still not public - which is fine and should stay that way imo (as shown by unauthenticated API request), but I think you made it so that I, as a member of the org, can see the core and contributors team (I forget if I could before though).

[bmpvieira]

I guess there's really no reason why they shouldn't be public (also since we are trying to display them in the website). It's just a matter of figuring out how GitHub settings. Anyway, great that it's working now. I'll be waiting for the PR 👍