Use all-contributors-cli to generate contributors list

[jfmengels]

Update README.md and .all-contributorsrc to use all-contributors-cli v2.0.0.
It is currently in beta (npm i -g all-contributors-cli@beta).

• Contributors are listed in .all-contributorsrc, next to the generation settings.
• The generator uses the contributor list in .all-contributorsrc to generate the list of contributors (using all-contributors generate)
• If you want to modify the data of a contributor, do it in the rc file, then run the generator again.
• If you want to add a contributor, run all-contributors add <githublogin> <contributions>. For example all-contributors add kentcdodds doc,review. The contributor's data will be fetched from GitHub, and the avatar will link to his "blog" if available, otherwise to his github page).
• The badge count is updated at every generation.
• The tool uses comment tags, like <!-- ALL-CONTRIBUTORS-LIST:START --><!-- ALL-CONTRIBUTORS-LIST:END --> to find where to inject the contributor list and the badge list.
• I have added the possibility to define custom templates for most of the generations
• It's possible to configure the tool to go update multiple files, like README.md and CONTRIBUTORS.md. If for example, there is only the badge in the former and the contributor list in the latter, both will be updated (as long as the appropriate comment tags are present).

Let me know what you think!

Preview of the README here

[chrissimpkins]

Looks great @jfmengels! Really like the ability to add new contributors to the .all-contributorsrc JSON on the command line.

[jfmengels]

Hmm... There are some differences between the GH markdown render and the Atom plugin's.

I see that the table now has kind of a grid, and I think I found out how to repair it. Not that I want this to turn into a cosmetic discussion, but which one do you prefer? Grid or no grid?

Also, the badge is on a different line than the other badge. Will have to make a better content injector I guess (currently the tags have to be on separate lines, and at the beginning of each). I kind of like that implementation simplicity ^^'

Thanks @chrissimpkins, it was @kentcdodds's idea to have them all in a rc file :)

[chrissimpkins]

Is it possible to use those contributor list tags in a separate CONTRIBUTORS page or does it need to be in the README?

[jfmengels]

@chrissimpkins You can do it in any file that you want. There is a filesoption that you can put in the rc file (which defaults to ['README.md']. So if you want to put the list in the CONTRIBUTORS.md file, set files to be either ['README.md'] or ['README.md', 'CONTRIBUTORS.md] and move/put the

<!-- ALL-CONTRIBUTORS-LIST:START -->
<!-- ALL-CONTRIBUTORS-LIST:END -->

in there.

[chrissimpkins]

fantastic. this is great!

[jfmengels]

Also noticed that @fhemberger's name makes the table formatting worse as I put back his whole name. Shall I shorten his name again like he himself offered to, or shall we use 6 columns (already configurable)? It might be simpler to just use logins, as some people will have crazy long names and the formatting will then explode even with like 2 contributors.
(but then again, this might be a discussion for another time/thread)

[kentcdodds]

6 columns please.

Will comment more later. This is fantastic!

[jfmengels]

6 columns you go! (took just a config change and a regeneration)
Just as a FYI: I've had to edit a few things by hand, as they were different from what I got by simply adding you guys to the project. For example, @Jameskmonger's name on GitHub is different from what he added in the list, and @kentcdodds "blog" is different from what is in his profile (though in this case they get redirected to the same thing).

[kentcdodds]

Really sorry it's taken so long for me to get to this. Looking at it now!

[kentcdodds]

Any way we can get rid of these extra empty cells? I think they look funny...

Also, it appears that the names on the top row are bold but not the names on the bottom...

Not a huge fan of comma-first style personally. But that's a nit-pick...

Also, I'd like the ability to have the badges inline (as they are now). Is that possible?

Other than those things, this is great!

[jfmengels]

@kentcdodds

Any way we can get rid of these extra empty cells? I think they look funny...

Sure, I don't care that much either way. Does anybody else want to bikeshed on this?

it appears that the names on the top row are bold but not the names on the bottom...

I think it's because the top row is considered to be the column title row and is therefore made bold by the markdown renderer. If so, this is good enough of a reason to split the table into 1 table per line and getting rid of those extra empty cells.

Not a huge fan of comma-first style personally. But that's a nit-pick...

I'm not that fond of comma-first either, but I made the rc file like that because I'm hoping it will create less conflicts should two contributors be added in different PRs or should a contributor get new contribution types in different PR. I'm not convinced that this will help much, but if can help a bit, I think it's worth it. What do you think?

Also, I'd like the ability to have the badges inline (as they are now). Is that possible?

I don't see what you mean. This is what I had before

and what I have now

Care to explain the difference?
(notice that we again don't see emojis the same way :D)

[kentcdodds]

I'm not that fond of comma-first either, ...

I know with .babelrc and .eslintrc you can actually provide invalid JSON and it parses just fine. Meaning you don't have to quote keys and you can have comments and (most noteabily) you can do comma-dangle style which I am much more fond of. Maybe you could look into how they parse those RC files...

I'm talking about these badges :-)

[jfmengels]

Oh, yeah, those badges, obviously ^^
I thought they would like fine because they did so in the Atom markdown preview. I'm not sure how to do that. Yeah that is possible, although a bit more of a pain that I would like to, but I will definitely work on it.

[kentcdodds]

Yeah, it'd just need to be able to have the open comment, badge, and closing comment on the same line and I think it'd work.

[jfmengels]

As for comma-dangle style, I'm not fond of having to force other tools that would like to read the rc file to parse invalid JSON.

[kentcdodds]

rc files are quite common actually. Babel and ESLint use them. Here's a module you could use to get the config from multiple sources which would actually allow people to configure all-contributors-cli in many different ways: https://github.com/davidtheclark/cosmiconfig 👍

[jakebolam]

Closing. AWESOME WORK. In the readme and repos now