See specific line annotations in GitHub Checks when PR fails lint job | Feature Requests

See specific line annotations in GitHub Checks when PR fails lint job

Cormac

This would permit the user to see exactly what lines failed to lint via GitHub Checks.

CCI-I-648

October 22, 2018

Gray Watson

I've written a free maven plugin and service which does this sort of thing. It's specifically designed to process Java surefire output but happy to work with folks to support other languages/output. See: https://github.com/j256/simplelogging/runs/1818758884 Here's the hold page for the integration: https://github.com/apps/test-check-publisher

Alan Yan

Hi, has there been any update with this?

Daniel Compton

I would really like to see this too. The lack of this feature, and generally weak integration with GitHub Checks makes me think about looking at other CI systems.

Corey Capel

Would love this feature as well. As it is now, we can't use CircleCI as a Github Checks runner because there's no way for us to send back status, completion, result, or annotation info back to the Github Checks API.

Shortest path to enabling this capability could involve CircleCI adding a

github_checks

option to workflow and/or job config that exposes the result and annotation responses.

Richard Macklin

I was really excited after seeing the announcement that CircleCI finally supports the GitHub checks API: https://circleci.com/blog/see-the-status-of-your-circleci-workflows-in-github/
I've been eagerly awaiting this since GitHub announced the Checks API in May:
https://blog.github.com/2018-05-07-introducing-checks-api/
https://developer.github.com/changes/2018-05-07-new-checks-api-public-beta/
In that GitHub blog post, as well as in the following help article and API docs, they describe how GitHub Checks can provide annotations for individual lines of code (e.g. for violations found by the linter):
https://help.github.com/articles/about-status-checks/#checks
https://developer.github.com/v3/checks/runs/#annotations-object
Unfortunately, CircleCI's integration with the GitHub Checks API doesn't currently support this. This is the GitHub Check API feature that I've been most looking forward to, because it will allow us to see things like lint failures without having to leave GitHub to scroll through a specific CircleCI job's log.