Describe the bug
The documentation for both the bot and the cli clearly lists that it's possible to sort contributors alphabetically, but that the default is false. It doesn't say how they will be sorted when set to false. Presumably the chronological order in which they were

Problem

https://github.com/blockstack/blockstack/blob/master/engineering/README.md

This document is far too large and contains manual steps (error-prone, must be remembered).

The process should be "build-in" to tools. As an example, the github-issue-tracker is not capable to model a more complex workflow.

If you favor "Sprints", use a tool where you can file the sprints.

If you f

Problem description: on small screens table cells have uneven widths which looks odd.

This seems to be related to the length of the username and word wrapping.

Reproduction repository: https://github.com/ehmicky/portable-node-guide

Must be looked a

Is your feature request related to a problem? Please describe.
The bot currently decides whether to 'init' (install the placeholders for the table and badge) for the README if there is no .all-contributorsrc file. If the file is found, it skips this step. This causes the bot to crash if a user has an .all-contributorsrc file but has nothing else.

Describe the solution you'd like
H

In ipfs-shipyard/js-ipfs-contributors#2, we'd like to annotate the contributors list with celebratory emoji (🥳).

It looks like the best place to add a feature like that might be here in NYC.

Are you open to a config option that would make the extra queries and add a flag if the contribution was a first one for a given user in a given repo?

Would be great to have recommendations on licensing for TH open source projects.

What license(s) have been approved by legal?

Reminders to check the licenses of project dependencies (and notes on when we need to reject libraries / other dependencies for licensing reasons)

sphinx_js is the equivalent of autodoc for Javascript. It's a third-party extension for Sphinx, which means ReadtheDocs can't run it for us. Instead, we need to set up a fork, run it manually on that fork, and then bring the output over to our main repository and figure out a way to get it up on ReadtheDocs. Someone needs to get that all set up and working.

Use a resolver specific for this field, something similar to this:

Contributor: {
    firstContributionDate: firstContributionDateResolver,
  }

This based on this links of documentation:
Apollo docs resolvers
How to graphql