Bug: Silently ignoring errors when access_token has wrong scope

[itsdalmo]

Ref #48, it seems like check is silently ignoring errors (when the scope of the access_token did not grant private repository access. Most likely a 404 was returned, but whichever error was returned should have been output in the task and resulted in a non-zero exit code.

[itsdalmo]

I believe this might be related: shurcooL/githubv4#41. However, the Query() implementation should bubble up errors for non-200 status codes from the underlying client - and I would expect a 404 not found to be returned if the access token has the wrong scope 🤔