Use the GitHub's Checks API (fka Statuses API)
Open
help wanted
refactoring
- Dominant language
- Ruby
- Stars
- 16
- Forks
- 39
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 8
Description
GitHub just announced a new [status bar](https://github.com/blog/2040-clearer-mergability-information-for-pull-requests) under the comment section of the PRs. I think that the lint reviews would look better by using the [statuses API](https://developer.github.com/v3/repos/statuses/).
Contributor guide
Research direction
Start by reading the linked GitHub Checks and Statuses API documentation, then inspect how the bot currently publishes lint reviews. Done means lint results are represented in GitHub's pull-request status or checks interface as intended, rather than only through the existing review presentation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, ruby
- Domain
- ci-cd, devtools
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100