[riot-notifications] [RIOT-OS/RIOT] README: Add merge-chance badge (#15737)
notifications at github.com
Mon Jan 11 13:29:11 CET 2021
The RIOT community cares a lot about code quality.
Therefore, before describing what your contribution is about, we would like
you to make sure that your modifications are compliant with the RIOT
coding conventions, see https://github.com/RIOT-OS/RIOT/wiki/Coding-conventions.
### Contribution description
This adds a new badge to the README, which shows the chance of a PR of a non-member being merged and the number of days that takes. The information is taken from [this website](https://merge-chance.info/target?repo=RIOT-OS/RIOT) which was discovered by @benpicco. I personally find the numbers surprising, given that one of our problems we often discussed in the past was the perceived eternity it tags to merge PRs by new contributors. But maybe the good numbers come from our guilt. To quote @maribu from an offline discussion about this badge:
> Maybe the believe that we are slow on foreign PRs is motivating our fast response time. It would be interesting to see if the lack of guilt results in slower response time once we have this badge in the readme
Put here the description of your contribution:
- describe which part(s) of RIOT is (are) involved
- if it's a bug fix, describe the bug that it solves and how it is solved
- you can also give more information to reviewers about how to test your changes
### Testing procedure
Have a look at the rendered README. There should be the new badge now.
Details steps to test your contribution:
- which test/example to compile for which board and is there a 'test' command
- how to know that it was not working/available in master
- the expected success test output
### Issues/PRs references
Examples: Fixes #1234. See also #5678. Depends on PR #9876.
Please use keywords (e.g., fixes, resolve) with the links to the issues you
resolved, this way they will be automatically closed when your pull request
is merged. See https://help.github.com/articles/closing-issues-using-keywords/.
You can view, comment on, or merge this pull request online at:
-- Commit Summary --
* README: Add merge-chance badge
-- File Changes --
M README.md (3)
-- Patch Links --
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the notifications