You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have successfully pulled in the Github API with a token but when we send a post request it does not go through. Our belief is we cannot determine the correct syntax for the header to send with the post.
Github Docs suggests:
Creates a new repository for the authenticated user.
POST /user/repos
OAuth scope requirements
When using OAuth, authorizations must include:
public_repo scope or repo scope to create a public repository
repo scope to create a private repository
Error messages or screenshots
Steps attempted to resolve the issue
We attempted to inject the information directly into our post request.
We verified the token work through postman for accessing an account with a get request.
We attempted to access the create a post request with the same access token but received an error.
Description of issue
We have successfully pulled in the Github API with a token but when we send a post request it does not go through. Our belief is we cannot determine the correct syntax for the header to send with the post.
Github Docs suggests:
Creates a new repository for the authenticated user.
POST /user/repos
OAuth scope requirements
When using OAuth, authorizations must include:
public_repo scope or repo scope to create a public repository
repo scope to create a private repository
Error messages or screenshots
Steps attempted to resolve the issue
We attempted to inject the information directly into our post request.
We verified the token work through postman for accessing an account with a get request.
We attempted to access the create a post request with the same access token but received an error.
Research
https://python-social-auth.readthedocs.io/en/latest/use_cases.html#signup-by-oauth-access-token
https://developer.github.com/v3/repos/#create-a-repository-for-the-authenticated-user
The text was updated successfully, but these errors were encountered: