GitHub has introduced "Checks API", which states:
The Checks API allows you to build sophisticated tools for continuous integration (CI), linting, and acceptance testing on GitHub.
I've created a bot, based on probot(Node.js based), which posts a check run with CircleCI screenshotter results, as screenshotter is hard to run and CircleCI build artifacts are hard to access.
https://github.com/KaTeX/screenshotter-bot




This is awesome! I love that diffs from failures show up right in the GitHub UI.
Transfer the repo to KaTeX organization
Sorry I still haven't gotten around to this. Knowing why this is necessary will me advocate transferring of the repo.
@kevinbarabash I meant moving the bot repo(https://github.com/ylemkimon/screenshotter-bot) to the KaTeX organization. That way, it's easier to maintain, and other people can easily review and contribute to the code.
Is it possible to run lint, flow, and/or jest via this API too?
@edemaine There is annotation feature in the check:


I think Travis CI or CircleCI will support exporting results to CI.
I didn't know it was installed on the repo 馃槃 As it's running on my laptop, its uptime would be only when I'm debugging it or I forgot to turn off it after the debugging :)
Thanks for the update.
The issues has been resolved and I think it's ready to be deployed. @kevinbarabash Can I transfer the bot repo's ownership to the KaTeX?
@ylemkimon go for it. Thanks for setting this up.
@kevinbarabash Done 馃槃 Please update the author/copyright information appropriately.
@ylemkimon just so that we're on the same page, you think we should change the copyright to
Khan Academy (c) 2018
@kevinbarabash Yes, I'm willing to waive all my rights if necessary.
Also, it seems creating a GitHub app on the organization requires admin permission. Could you create a GitHub app and deploy the bot? (I think we can go with Zeit Now).
The bot is successfully deployed!
I forgot to enable Pull request permission and event subscription, which is needed for PR from forked repo. I enabled them and re-authentication may be necessary.
@ylemkimon I've accepted the updated permissions.
@kevinbarabash Thank you!