|GitHub Checks API For Continuous Integration|
|Written by Alex Armstrong|
|Friday, 11 May 2018|
GitHub has announced a beta public release of a new Checks API that aims to make it possible to integrate code checks into a continuous integration workflow. It is the first feature built specifically for repositories with Travis CI GitHub Apps integration enabled. Checks API compatibility with CircleCI is on the way.
The Checks API, which allows developers to build sophisticated tools for continuous integration (CI), linting, and acceptance testing on GitHub is now available in public beta. This new functionality currently works with the GitHub REST API, with GraphQL support coming soon.
It provides new functionality which allows integrations and GitHub to communicate more comprehensively about the checks run against code changes. These changes will improve workflow by allowing users to view feedback from code checks directly in the pull request view, see the line of code causing a problem in the diff view, “re-run” checks, and more-all within the GitHub user interface.
The GitHub Checks API can be regarded as an evolution of the traditional GitHub status API, which allows external services to mark commits with a status code, i.e.
For Travis CL projects on GitHub Apps, GitHub Checks API allows you to view build stages, jobs, and results, so you can get a complete picture of the health of your projects directly from GitHub. You can also see your config and re-run builds from within the GitHub Checks UI. An additional “Checks” tab in a Pull Request where you will see Travis CI listed. The GitHub Checks page shows a detailed summary of your build and gives you the ability to re-run it directly from the GitHub Checks page.
or email your comment to: email@example.com
|Last Updated ( Friday, 11 May 2018 )|