First, thanks for providing a simple tool for working with Github releases!

It appears that when using the upload command to a non-existent repository, the access_token is leaked in the error message. This is a problem when running this tool in an open-source project's CI system.

bin/linux/amd64/github-release
error: expected '200 OK' but received '404 Not Found' (url: https://api.github.com/repos/envoy-bot/envoy/releases?access_token=MY_ACCESS_TOKEN&per_page=100)