For those like me who might find this and wonder how the suggested workaround affects the tutorial. In Step 1.1 Updating app permissions, perform the following additional steps: In the "Permissions" section, find " Pull requests ", and select Read-only in the Access dropdown next to it. In the "Subscribe to events" section, select Pull Request to subscribe to that event. In Step 1.2 Add Event Handling, paste this modified version of the check_suite route so that it can also handle a pull_request event. case request.env['HTTP_X_GITHUB_EVENT'] when 'check_suite' # A new check_suite has been created. Create a new check run with status queued if @payload['action'] == 'requested' || @payload['action'] == 'rerequested' create_check_run end when 'pull_request' # A new check_suite has been created. Create a new check run with status queued if @payload['action'] == 'opened' || @payload['action'] == 'updated' create_check_run_from_pull_request end end In Step 1.3 Creating a check run, under helpers do, add this create_check_run_from_pull_request method: # Create a new check run with the status queued
# # At the time of writing, Octokit does not support the Checks API yet, but
# it does provide generic HTTP methods you can use:
check_run = @installation_client.post(
# This header allows for beta access to Checks API
# The name of your check run.
name: 'Octo RuboCop',
# The payload structure differs depending on whether a check run or a check suite event occurred.
end In Troubleshooting, encourage Github to acknowledge this limitation and workaround.
... View more