all-contributors/app

🤖 A GitHub App to automate acknowledging contributors to your open source projects

Call for translators! We're looking for translators to help translate this spec for everyone!

Read this documentation in the following languages

한국어	中文	Bahasa Indonesia	Deutsch	Polski
English	Português do Brasil	Español	Français	Русский	日本語

This is a specification for recognizing contributors to an open-source project in a way that rewards every contribution, not just code.

The basic idea is this:

Use the project README (or another prominent public documentation page in the project) to recognize the contributions of members of the project community.

People are giving themselves and their free time to contribute to open source projects in so many ways, so we believe everyone should be praised for their contributions (code or not).

The All Contributors Table

Below is an example of how using the all-contributors spec table can recognize all contributors

You can use the @all-contributors bot 🤖 to automate acknowledging contributors to your open source projects

Specification

The specification is detailed on allcontributors.org

Emoji key

The Emoji Key ✨ (and Contribution Types) can be found on allcontributors.org

Contributing

If you've ever wanted to contribute to open source, and a great cause, now is your chance!

See the contributing docs for more information

Contributors ✨

Thanks go to these wonderful people (emoji key):

Kent C. Dodds 💬 📖 👀 📢	Jeroen Engels 📖 👀 🔧	Jake Bolam 📖 🔧 🚇 🚧 👀 💬	Tyler Benning 🚧 💻 🎨	Jeff Wen 🚧 👀	Maximilian Berkmann 🌍 📖 🚧 👀 📢	Matheus Rocha Vieira 🌍 💻 📖
Robert Lluberes 🌍	이종진 📖 🌍	Wenqing Xue 🌍	Divjot Singh 📖 👀	Ben Briggs 📖 👀	James Monger 📖	Chris Simpkins 📖 👀
F. Hemberger 📖	Daniel Kraft 📖	Mayank Badola 📖 🔧	Marco Biedermann 🎨	Itai Steinherz 📖	Patrick Connolly 📖	Nikola Đuza 📖
Demian Dekoninck 💻	Michael Peyper 📖	David Sima 📖 🌍	allcontributors[bot] 📖	Greenkeeper[bot] 🚇	Maryam Pazirandeh 📖	Cassandra Venere 📖
codimiracle 📖	Sung Kim 🌍 📖	Thomas Brok 🌍	robertgrzonka 🌍	Megumi Aliya 🌍	Yule 🌍	Sylvain Pace 🔌
Peter Hürlimann 🌍	Thiago Delgado Pinto 🌍	Rogerio Prado de Jesus 🌍	Tobias Andersen 🌍	danielbronder 🌍	João Pedro Raskopf 🌍	Edwin Vargas 🌍
Faisal KANOUT 🌍	John Murphy 📖	Kirstie Whitaker 🤔	Patryk Peas 📖 🌍 💻	Ivan.Nginx 🌍	levy 📖	nils måsén 📖
Masato Urai (@uraway_) 🌍	Kyle Holmberg 📖	Simon Aronsson 🌍	Cem 🌍	Jérémie Astor 📖	Rachel M. Carmena 🌍	SnO₂WMaN 📖
César Richard 📖 📓	kharaone 📖	Mudassar Ali 📖	Andrew Mason 📖	Mauro M. 📖	Nicolas Goutay 📖	William Entriken 💻
Amine 📖	Stefano Moia 📖	Adam Tuttle 📖	Moni 🚇	Ilaï Deutel 📖	Hendrik Brummermann 📖	Sang Lostrie 🐛
xinbenlv 📖	Ivan Paulovich 📖	Jake Wiesler 📖	Micael Jarniac 🐛	Markus Löning 📖	Austin Huang 📖	Nils Andresen 📖
LaChapeliere 📖	Michal 🌍	Ali Torki 📖	Josh Soref 📖	Taiizor 💻	Ikko Ashimine 📖	Matthew 📖
Cornelius Roemer 🎨	JohnnySD 🖋 📖	mwaitzman 📖	Kenichi Kamiya 📖	Angel Aviel Domaoan 📖 💻 🚧 🐛 👀	Allan Bowe 📖	E - Coders (Aasheesh Agarwal) 📖
Fernando 📖	Vedant Mohan Goyal 📖	Muhammad Hanis Irfan Mohd Zaid 📖	Abe Hanoka 📖	Roshan Jossy 📖 💻	Sébastien Lavoie 🐛	Nicolas Girondi 🌍
Federico Grandi 📖	Henry Bley-Vroman 📖	LBF38 📖	Yoon Hyeseong 🐛

This project follows the all-contributors specification. Contributions of any kind are welcome!

LICENSE

MIT

app's Issues

The bot incorrectly respects the config file for options it should know

Describe the bug
The bot incorrectly respects the config file for options it should know.

Click the 💻icon on a contributor in the Contributors section

See that it incorrectly links to an invalid URL: https://github.com/all-contribtuors/bot/commits?author=jakebolam

This URL is determined based on the config in .all-contributorsrc which is miss-configured.

The bot should ignore the following config options (when running in bot mode):

  "projectName": "bot",
  "projectOwner": "all-contribtuors",
  "repoType": "github",
  "repoHost": "https://github.com",

Expected behavior
We know the repo and server, let's ignore the config and go with what we know

Screenshots

Add APM monitoring such as datadog

Is your feature request related to a problem? Please describe.
It's difficult to gain visibility into the instance running in production.

Describe the solution you'd like
Add APM monitoring to have visibility into production. (CloudWatch is not enough)

Describe alternatives you've considered
NewRelic etc

Additional context

Better error handling when the configuration file data structure is incorrect

Is your feature request related to a problem? Please describe.
When the configuration file datastructure is incorrect,the bot fails in weird and wonderful ways. e.g.

{
    "projectName": "coding_challenge-13",
    "projectOwner": "zeroDevs",
    "repoType": "github",
    "repoHost": "https://github.com",
    "files": [
        "README.md"
    ],
    "imageSize": 100,
    "commit": true,
    "contributors": [
        {
            "login": "The24thDS",
            "name": "David Sima",
            "avatar_url": "https://avatars0.githubusercontent.com/u/26633429?v=4",
            "profile": "https://github.com/The24thDS",
            "contributions": [
                "code",
                "bug",
                "review"
            ]
        },
        {
            "login": "mikeattara",
            "name": "Mike Perry Y Attara",
            "avatar_url": "https://avatars1.githubusercontent.com/u/31483629?v=4",
            "profile": "https://mikeattara.com",
            "contributions": [
                "ideas",
                "code",
                "review",
                "test"
            ]
        },
        {
            "login": "AkinAguda",
            "name": "Akinwunmi Aguda",
            "avatar_url": "https://avatars0.githubusercontent.com/u/39712415?v=4",
            "profile": "https://github.com/AkinAguda",
            "contributions": [
                "bug"
            ]
        },
        {
            "login": "jakebolam",
            "name": "Jake Bolam",
            "avatar_url": "https://avatars2.githubusercontent.com/u/3534236?v=4",
            "profile": "https://jakebolam.com",
            "contributions": [
                "question"
            ]
        },
        {
            "login": "aneagoie",
            "name": "Andrei Neagoie",
            "avatar_url": "https://avatars3.githubusercontent.com/u/10776230?v=4",
            "profile": "https://github.com/aneagoie",
            "contributions": [
                "bug",
                "code",
                "ideas",
                "review"
            ]
        },
        {
            "login": "MattCSmith",
            "name": "Matt Smith",
            "avatar_url": "https://avatars3.githubusercontent.com/u/6190356?v=4",
            "profile": "https://github.com/MattCSmith",
            "contributions": [
                "question",
                "bug",
                "code",
                "ideas",
                "review"
            ]
        },
        {
            "contributions": [
                "ideas"
            ]
        },
      ]
}

Technically valid JSON but the schema is busted.

Describe the solution you'd like
Provide great error messages, so users no whats wrong with the schema.

Even better: Auto fix it!

Additional context
See: https://sentry.io/all-contributors/github-bot/issues/859146506/?query=is%3Aunresolved

Also issues: zeroDevs/FullstackTrends_Challenge-13#182

Add status up-time

Is your feature request related to a problem? Please describe.
Public visibility into up time

Describe the solution you'd like
Add status uptime, something like https://stats.uptimerobot.com/Dq46zf6PY

This can also be added to our marketplace listing

Describe alternatives you've considered

Additional context

Bot currently overwrites contributions if user exists (does not add to them)

Is your feature request related to a problem? Please describe.
The bot's PR currently overwrites previous contributions (does not add to them)

Describe the solution you'd like
When a user already exists merge the contributions, instead of replacing them.

Describe alternatives you've considered

Additional context
#9

Invalid Code contribution URL

Describe the bug
When I click on the 💻 on the emoji key it uses what appears to be an invalid URL: https://github.com/all-contribtuors/bot/.
Which in fact is caused by the typo in all-contributors.

To Reproduce
Click on any 💻, ⚠️ or 📖 emojis and it will be using the typoed URL.

Expected behaviour
The URL should be working.

Screenshots
Not needed

Additional context
This doesn't seem to be happening on the CLI and I couldn't found thus far where the typo was on both repos (using master up-to-date).

In some cases, seeing two responses from the bot

Describe the bug
In some cases seeing two responses from the bot:

To Reproduce
Steps to reproduce the behavior:

1. @all-contributors please add @tbenning for design
   Repeat until seen

Expected behavior
One response per comment

Screenshots
See above

Additional context
The second error message is relating to: https://sentry.io/all-contributors/github-bot/issues/844367677/. I.e. the method is being invoked twice, and the second time fails on creating the branch. This is being fixed as part of #48. In this case tho it will still result in 2 comments to the users.

Looking at deliveries from GitHub there are 'service timeouts' at the time (with payload relating to this message), causing the double delivery.

AllContributorsBot should be able to setup repo's initially

Is your feature request related to a problem? Please describe.
When you type @all-contributors please add jakebolam for code and the repository is not setup. The bot responds and says use the CLI tool to setup the repo.

tldr: Remove project dependence on cli tool!

Describe the solution you'd like
It would be good if the bot could open an initial PR in these cases (or direct the user to say some other specific words for the bot to put up an init PR).
e.g.
@AllContributorsBot setup project
-> Puts up initial pull request for README.md and .all-contributorsrc

Describe alternatives you've considered
Keeping setup restricted to using the cli tool

Additional context

An easy way to refresh a pull-request adding a contributor

Is your feature request related to a problem? Please describe.
When multiple contributors are being added, a PR could become stale (i.e not up to date with master/conflicts with the master branch). We should have a way to auto resolve this.

Describe the solution you'd like
@all-contributors please refresh this PR

Describe alternatives you've considered
Alternatively, we could watch for merge event son pull requests opened by the bot, and refresh the PR:

Additional context

Support adding multiple users in a single message (Use NLP parsing per sentence, not on an entire message)

Is your feature request related to a problem? Please describe.
It would be great to have a way to bulk add users in a single request.

Describe the solution you'd like
Implementing per sentence parsing instead of per-message will allow us to do this. It will also help the NLP to be more effective in determining intentions.

Describe alternatives you've considered

Additional context
Case of a user adding lots of users: zeroDevs/FullstackTrends_Challenge-13#161

Broken case on message too big:
https://github.com/zeroDevs/coding_challenge-13/issues/132#issuecomment-457773736

Case of not working:
See freecodecamp-ibadan/freecodecamp-ibadan#4

@all-contributors please add @stevoo24 for code,content

Just a test

I just want to see this in action! This is sooooo cool!

@AllContributorBot please add kentcdodds for infrastructure

Commit convention agnosticism

Is your feature request related to a problem? Please describe.
A feature

Describe the solution you'd like
The bot should be aware of the commit convention a repo, it was installed on, uses in order to write valid commits and valid PRs.

Describe alternatives you've considered
Allowing repo maintainers to set/specify the commit convention whether it's via a CZ config or via a commitConvention (or commitStyle) field in the .all-contributorsrc file.

Additional context
Here's an example of PR using the angular one on a repo set to ESLint with commit linters.

Improve development experience

Is your feature request related to a problem? Please describe.
Local development experience is currently confusing with probot and serverless runners.

Describe the solution you'd like
Just use serverless:

• Run lambdas in serverless (see #86)
• Create a serverless plugin to allow use of smee proxy in development -> Now in #188
• Document development experience
• Remove yarn start-probot
• Update yarn start to use yarn start-serverless

Setup sandbox environment we can sanity test against before shipping to production

Is your feature request related to a problem? Please describe.
Shipping some changes straight to production is risky

Describe the solution you'd like
A sandbox environment we can run sanities against before heading to production

Describe alternatives you've considered
Keeping as is

Additional context
This should stay as part of the master branch, and if possible the sanities should be automated

Bot links to incorrect pull request when updating

Describe the bug
Bot links to wrong pull request when updating

To Reproduce
Steps to reproduce the behaviour:

1. Mention: @all-contributors please add @tbenning for design, leave the PR open
2. Mention: `@all-contributors please add @jakebolam for design, leave the PR open
3. Mention: @all-contributors please add @tbenning for design, see that comment links to jakebolam PR, (tbenning PR was updated tho)

Expected behavior
Links to the correct pull request

Screenshots

Additional Context
See comment in sandbox: all-contributors-sandbox/test-all-contributors#1 (comment)

Receive messages if only for bot name

Is your feature request related to a problem? Please describe.
Messages for the bot should only be processed if it starts with @AllContributorsBot.
Currently, the bot will respond to names such as @AllContributorsBotDev, and anywher in the message

Describe the solution you'd like
Just respond to bot name, if the entire message is directed at said bot.

Describe alternatives you've considered

Additional context

When a user is found, but the bot cannot determine contributions, tell the user

Is your feature request related to a problem? Please describe.
Sometimes when asking the bot to add contributions it won't be able to determine the types of contributions, this does not stop the bot opening a PR with an empty array of contributions see https://github.com/all-contributors/all-contributors-bot/pull/29/files#diff-c47fb5a6d4fde805d2706fc934e8d354R38

Describe the solution you'd like
When a user is found, but the bot cannot determine contributions, tell the user. A PR should not be opened.

Describe alternatives you've considered

Additional context

Add basic CloudWatch alarms

Is your feature request related to a problem? Please describe.
If users start depending on the bot, they want it to work. Let's ensure we know when it's not.

Describe the solution you'd like
Cloud watch alarms on error rate increases etc.
Measuring timing would be important too, too fast and something is wrong, same as too slow.

Describe alternatives you've considered

Additional context
Something like https://github.com/ACloudGuru/serverless-plugin-aws-alerts could help, instead of pure cloud formation

Switch documentation examples to add @user instead of add user

@user is far more reliable, both for the UX seeing which user your adding and the bot, determining which user to add. Let's update the documentation so our preferred method is add @user

Support adding people with mentions

Is your feature request related to a problem? Please describe.
Adding a user using @all-contributors please add @tbenning for design results in a fail

While non-mentions succeed:

Describe the solution you'd like
Adding them for their contributions!

Describe alternatives you've considered

Additional context

Write article about the new bot!

Is your feature request related to a problem? Please describe.
Promote the new bot

Describe the solution you'd like
Write a blog article about the new bot

Describe alternatives you've considered

Additional context

Support default branches other than master

Is your feature request related to a problem? Please describe.
Currently only supports pull-requests again master

Describe the solution you'd like
Should look at default branch, and base pull-reuqest against that branch

Describe alternatives you've considered

Additional context

List of common gotchas

Describe the solution you'd like
List of common gotchas (possibly on the website)

Support @allcontributors when requesting additions

Is your feature request related to a problem? Please describe.
@allcontributors add @The24thDS for code without a dash doesn't work

Describe the solution you'd like
To see the non dash version work!

error.code deprecation

Describe the bug
Since @octokit/[email protected], deprecation warnings pops up so it would be ideal to update the relevant code snippet.

To Reproduce
Steps to reproduce the behaviour:

1. yarn test or npm test
2. Wait for the following test suites to finish: test/utils/getUserDetails.test.js, test/index-e2e.test.js
3. Look out for console.warn outputs.

Expected behaviour
This shouldn't be happening

Screenshots
If applicable, add screenshots to help explain your problem.

Additional context

console.warn node_modules/@octokit/request/lib/http-error.js:15
`error.code` is deprecated, use `error.status`. 

Sentry is not working on lambda

Investigate and fix sentry for lambda probot/adapter-aws-lambda-serverless#11

Additions in batches (or docs for this)

This bot is so awesome!!! 🙌 👍 🎉 🤖

We often have more than one new contributor per day, so:

We are interested in running this in a batch each week to reduce PR churn and maintenance burden.

If this is already possible, apologies, and could you point us at the docs?

Otherwise we'd love to install and use this app if such a feature were eventually added. Thanks a million!

Add analytics

Is your feature request related to a problem? Please describe.
It would be good to have insight into how users are using the bot

• How many messages result in a PR (effective % rate)
• Common usage terms.
• What messages fall down (note we should only record this for PUBLIC repositories)

Describe the solution you'd like
Some analytic tracking solution

Describe alternatives you've considered

Additional context

Consider adding CI check (when all-contributors rc is manually changed)

Is your feature request related to a problem? Please describe.
When a user manually adjusts the all-contributors file its possible it could be broken.

Describe the solution you'd like
Add a CI check which says (this PR is all contributors good to go)

Describe alternatives you've considered

Additional context
See #102

An in-range update of serverless is breaking the build 🚨

The devDependency serverless was updated from 1.36.3 to 1.37.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

serverless is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

• ✅ ci/circleci: node_modules: Your tests passed on CircleCI! (Details).
• ❌ ci/circleci: test: CircleCI is running your tests (Details).
• ✅ ci/circleci: lint: Your tests passed on CircleCI! (Details).
• ❌ ci/circleci: build: Your tests failed on CircleCI (Details).

---

Release Notes for 1.37.0 (2019-02-06)

• Fixes for AWS cors config issues
• Preserve whitespaces in single-quote literal fallback
• AWS: Add fallback support in ${cf} and ${s3}
• Throw an error if plugin is executed outside of a serverless directory
• Require provider.credentials vars to be resolved before s3/ssm/cf vars
• Provide multi origin cors values
• handle layers paths with trailing slash and leading ./ or just .
• Resolve profile before performing aws-sdk dependent actions
• Fix assuming a role with an AWS profile
• Allows Fn::GetAtt with Lambda DLQ-onError
• Fix #5664 - Rollback fails due to a timestamp parsing error
• AWS: Tell S3 bucket name and how to recover if deployment bucket does not exist
• Do not print logs if print command is used.
• Default to error code if message is non-existent
• Add resource count and warning to info display
• Add uploaded file name to log while AWS deploy
• Enable tab completion for slss shortcut
• Upgrade google-cloudfunctions to v2 and set defaults to node8 etc
• Convert reservedConcurrency to integer to allow use env var

Meta

• Comparison since last release

Commits

The new version differs by 114 commits.

• 2cf96e0 Merge pull request #5803 from serverless/release-1-37
• 1b8252d releasing v1.37.0
• 3b9957f Merge pull request #5794 from serverless/fix-tests-debug
• c551abf fixed cli tests when running in debug mode
• 4a64f4a Merge pull request #5793 from serverless/fix-yml-race-condition
• 5896f0c fix race condition when loading config file
• 04a2a65 Merge pull request #5788 from serverless/secrets-via-ssm
• cefe6f0 Add aws secrets mgr to TOC of aws vars
• 74a1260 Update docs/providers/aws/guide/variables.md
• 2e49692 Update docs/providers/aws/guide/variables.md
• ff82197 Document how to use Secrets Manager
• 61d3af3 Merge pull request #5785 from pchynoweth/master
• 4c935d1 Fixed up linting issues
• 9a25ade Added unit tests
• 73d95c2 Fixed linting issue

There are 114 commits in total.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

avatarBlock is not defined in fileContentModifierFunction, line 58

Describe the bug
Sentry issue: https://sentry.io/all-contributors/github-bot/issues/881644816/

Affecting: freecodecamp-ibadan/freecodecamp-ibadan#4

Reason

For some reason the bot was crashing trying to find the users avatar.

Add usage documentation to website

Describe the solution you'd like
We should document installation and usage on the website!
https://github.com/all-contributors/website

Analytics: Track bot installs and uninstalls

Describe the solution you'd like
Track bot installs and uninstalls.

Could also track additional metadata with these (e.g. repository stars), uninstaller?

Additional context
Looking to gain more insight into how users are using the platform./

cc @tbenning @gr2m

all contributors responds to bot comments that are from 'user' accounts

Is your feature request related to a problem? Please describe.
Bot responds to other apparent bots

Describe the solution you'd like
Should not respond to bots

Additional context
See example here callstack/react-native-paper#827

Support full words (like infrastructure) instead of just keys like infra

Describe the solution you'd like
It would be great to support full words (like infrastructure, documentation etc) when requesting adds

Describe alternatives you've considered

Additional context

Support plurals when adding contributions e.g. docs (and doc)

Is your feature request related to a problem? Please describe.
@AllContributorsBot please add jakebolam for docs, infra and code results in the additions of infra and code (not doc as well)

Describe the solution you'd like
The bot should be able to understand plurals. And add doc as well.

Describe alternatives you've considered

Additional context

Convert code base to typescript or add JSDoc comments

Is your feature request related to a problem? Please describe.
Bugss

Describe the solution you'd like
Implement typescript to reduce type related bugs

Describe alternatives you've considered

Additional context

Lock down security on bot repo to allow write access to contributors

Is your feature request related to a problem? Please describe.
Maintainers should have write access to all repos, they currently do not have write access to the bot (due to security concerns).

Describe the solution you'd like
Lock down CI to only inject AWS secrets on master pushes.
Lock down AWS credentials to have the minimum credentials required for deployment.

Additional context
We don't pass environment variables (Secrets) to forked builds. Which is how we can currently have users fork the repo, put up pull requests and run the test builds.

On first install, remove need to create README.md file

Is your feature request related to a problem? Please describe.
On the first install, let's remove the need to create a README.md file as documented in the happy path install

Describe the solution you'd like
Auto create the file

Additional context

May need to use the https://octokit.github.io/rest.js/#api-Repos-createFile API in the Repository class

PRs opened by AllContributorsBot break the table

Describe the bug
The PR to add a contributor has broken the table. See https://github.com/all-contributors/all-contributors-bot/pull/21/files#diff-04c6e90faac2675aa89e2176d2eec7d8R39 for an example.

Expected behavior
Should correctly format table

Screenshots

Take advantage of lambda lifecycle and in-memory caching

Describe the solution you'd like
Take advantage of lambda memory freezing to lower start times when under load

Additional context
https://medium.com/@tjholowaychuk/aws-lambda-lifecycle-and-in-memory-caching-c9cd0844e072

This previous behaviour actually caused #91 (as it was miss-used).

Add caching to stats endpoint

Is your feature request related to a problem? Please describe.
Stats endpoint should have caching

Describe the solution you'd like
Add caching on api-gateway to only invoke the lambda every hour. See https://www.npmjs.com/package/serverless-api-stage#usage-example

Describe alternatives you've considered

Additional context
This may be chewing through our github quota

Handle case where branch already exists

Describe the bug
Bot currently crashes with `We had trouble processing your request. Please try again later. When the contributor branch already exists

To Reproduce
Steps to reproduce the behavior:

1. Comment and say @AllContributorsBot please add jakebolam for code, doc and infra
2. Wait for pull reuqest to be created
3. Comment again and say @AllContributorsBotDev please add jakebolam for code, doc and infra
4. See crash

Expected behavior
Should return and say a branch/PR is already open.

Screenshots

Additional context
After we fix this bug, it is likely we will expose the bug branch exist, but PR is not open. We should be wary of this case too.

sentry error of one such case: Error: Reference already exists
https://sentry.io/all-contributors/github-bot/issues/844367677/?query=is%3Aunresolved

First bot PR changed our table layout

(Thanks so much for building this!)

On first use with an existing contributors list (generated via the command-line tool), the bot sets contributorsPerLine to 7 in our config file. This is undesirable as the 7th column in each row is squished smaller than the others:

PR here

Open PRs on orgs using all-contributors to add the bot as a contributor

Describe the solution you'd like
Should we open PRs against projects using the all-contributors bot, so others are aware (I believe greenkeeper does this too)

Spreads awareness of the bot etc

An in-range update of all-contributors-cli is breaking the build 🚨

The dependency all-contributors-cli was updated from 5.9.1 to 5.10.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

all-contributors-cli is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details

• ✅ ci/circleci: node_modules: Your tests passed on CircleCI! (Details).
• ✅ ci/circleci: lint: Your tests passed on CircleCI! (Details).
• ❌ ci/circleci: test: Your tests failed on CircleCI (Details).

---

Release Notes for v5.10.0

5.10.0 (2019-01-16)

Features

• contribution-type: added maintenance type (#142) (292d400), closes #111

Commits

The new version differs by 1 commits.

• 292d400 feat(contribution-type): added maintenance type (#142)

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

Probot is using octokit/rest 15, which is missing some features e.g. git.getRef

Is your feature request related to a problem? Please describe.
AllContributorsBot requires some features not available in the current version of octokit/rest in the latest version of probot (7.4.0)
Error: Cannot read property 'getRef' of undefined")

Describe the solution you'd like
We need to bump the version of the octokit/rest api in probot

Describe alternatives you've considered
Cloning the repo locally and using git directly (instead of via github).

Additional context
Looks like the probot team is on it: probot/probot#774

In some cases user profile URLs are not being added correctly

Describe the bug
Users recently added to the contributor table:
https://github.com/all-contributors/all-contributors-bot#contributors

Have incorrect profile URLs: For example, Maximilian Berkmann links to https://github.com/all-contributors/all-contributors-bot/blob/master/maxcubing.wordpress.com

Expected behaviour
URLs are correct

Additional context
Not sure if this is in the CLI or the bot.

Usernames with brackets crash the bot

Describe the bug
@allcontributors[bot] add allcontributors[bot] for doc

To Reproduce

Expected behavior
To add a PR to add the user with brackets

Additional context
From sentry:
HttpError: refs/heads/all-contributors/add-allcontributors[bot] is not a valid ref name.

Looks like its trying to create the branch/ref with invalid semantics. The name for the branch will need to be escaped.

The bot is spamming when asked a question

Describe the bug
The bot is spamming when asked a question
Expected behavior
No spam

Screenshots

Additional context
Recently switched to sync worker on webhooks, passing all tasks to long run lambda 🤔