Closed tgetgood closed 6 years ago
login
to user
. I think that makes more sense.Otherwise, looks great!
I put some config examples in the README. Which part isn't clear? I'll elaborate on it.
As for login vs user, I was going for uniformity between repos and orgs. At the API level, they're both logins, but they're not both users.
We could do user
for repos and org
or orgName
or just name
for orgs.
How about
{
"token": "123435abcdf",
"repos": [{
"user": "mntnr",
"repo": "name-your-contributors",
"before": "2017-11-30",
"after": "2017-06-01"
}, {
"user": "mntnr",
"repo": "whodidwhat"
}],
"orgs": [{
"name": "adventure-js",
"after": "2017-07-01"
}]
}
Ah, missed that, sweet.
Hmm. If that is how GitHub's API does it, lets just stay with login. It works for both.
Sorry about the mangled rebase. Fixed now.
Not sure it's fixed? There's some reverts which are odd.
Was not fixed. This looks better.
Woop woop!
:tada: This PR is included in version 3.4.0 :tada:
The release is available on:
Your semantic-release bot :package::rocket:
Specified a config file format, example is
config.json.example
which is copied into the readme. Executingname-your-contributors --config config.json
spits out a copy of the config file with an extracontributions
key in each object which is what nyc would have spit out for that specific query.Note, this is branched off of the cli-updates branch. I can rebase it after that gets merged if there are any conflicts.
Addresses #29
I can't attach json files, so here are the examples:
config format:
Return format: