This would permit the user to see exactly what lines failed to lint via GitHub Checks.
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.
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.
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:
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):
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.
You won't be notified about changes to this idea.