Fixes #351
Also, what's the matter with "The pull-request cannot be merged due to conflicts"? I don't get where the conflicts are.

Please rebase on the current develop branch, you'll see that Validators have changed a bit (they are now simple functions).

Please rebase on the current develop branch, you'll see that Validators have changed a bit (they are now simple functions).

Not sure if rebase notifies by email, therefore leaving this comment :)

We usually don't add this type of markers.

Please add a docstring here. Also, I think that values would be a better argument name.

You can use result.ok to test for a non-error return code, that's what the requests API recommends.

I don't think that we should use a Github API token here. This token would need to be user-specific and we currently don't have a way for a user to do an Oauth2 session with GitHub.
Without the token we won't get private repos but that's not a problem for now.

You missed a vals argument here

Please describe the argument in the docstring using the format you'll see elsewhere in this file and in Hubs (Google-style).

You might as well just return result.ok.

As a general comment, also remember to run tox -e lint before pushing the PR to check for syntax and style errors.

Running the tests should have created two files in hubs/tests/vcr-request-data/, please include them in your pull request.

Running the tests should have created two files in hubs/tests/vcr-request-data/, please include them in your pull request.

Added mentioned files.