Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support specifying the content-type #115

Closed
brettcannon opened this issue Apr 19, 2020 · 1 comment · Fixed by #131
Closed

Support specifying the content-type #115

brettcannon opened this issue Apr 19, 2020 · 1 comment · Fixed by #131

Comments

@brettcannon
Copy link
Collaborator

Uploading a release asset expects an appropriate content-type for what is uploaded. Currently GitHubAPI always assumes a JSON payload.

@certik
Copy link

certik commented Aug 18, 2020

Mariatta added a commit that referenced this issue Aug 18, 2020
When the content-type is passed, the raw body is used in the request.
The default content-type is json, and the body would be parsed to JSON format.

Updated documentation and changelog.

Closes #115
Mariatta added a commit that referenced this issue Aug 23, 2020
Mariatta added a commit that referenced this issue Aug 23, 2020
* Allow passing content-type header to GitHubAPI.POST

When the content-type is passed, the raw body is used in the request.
The default content-type is json, and the body would be parsed to JSON format.

Updated documentation and changelog.

Closes #115

Co-authored-by: Brett Cannon <brett@python.org>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants