According to https://developer.github.com/v3/#parameters:
For POST, PATCH, PUT, and DELETE requests, parameters
not included in the URL should be encoded as JSON with
a Content-Type of 'application/json'
Closes#407.
Change-Id: Iee60a3ed6e06b85cc64f687fd28e7663c1fc34e3
Both of those endpoints use PUT method, which means they must send
the parameters as a JSON encoded body rather than query parameters.
Source: https://developer.github.com/v3/#parametersFixes#402.
Closes#403.
Change-Id: I444d1ce9ba881200282ff617454addc2e6eb4793
This is largely a style change. In the case of NewRequest and NewUploadRequest, it is completely a noop given current code (since a new request is created, and each header is added only one time). For BasicAuthTransport, it's a noop as long as incoming request doesn't already have "X-GitHub-OTP" header set (and if it did, then this is a better behavior to change its value rather than add a new one).
Even though these changes are largely noops, Header.Set is a simpler primitive to reason about, and it's more representative of the intended action. For "Content-Type", "Accept", and "User-Agent" headers, multiple such headers do not make sense, so it's better to use Header.Set than Header.Add.
Google no longer recommends CONTRIBUTORS files for projects, since this
data is better retrieved directly from version control.
Additionally, contributors are now instructed to add themselves (or
their employer, if appropriate) to the AUTHORS file, rather than the
maintainers being responsible for trying to keep this file up to date.
Ultimately, this should result in more accurate data, since in most
cases we don't know whether the code is copyright the contributor or
their employer.
Use Timestamp type for GistCommit CommitedAt field.
Add support for ListForks endpoint.
Add missing fields for GistCommit and GistFork types.
Closes#385.
Change-Id: If1379d83173d52c974bb5834a834d97aee2f0ad8
These changes are now official, so the custom media type is no longer
needed.
Fixes#381.
Fixes#382.
Updates #279.
Change-Id: I33cad47c6645c5292f699826ae117b94260a3044
Note that `TestUsers_Keys` still fails for general users
but will need to be addressed later.
Fixes#366.
Change-Id: I35d8a73c2daed08df7d60085b1585f48caee9a95
Note that this is an API-breaking change but should have minimal
impact on users of this package due to the nice inference
properties of the Go programming language.
Bumped `libraryVersion` to `2` due to API-breaking change as
discussed in #376.
Fixes#180.
Change-Id: Ib386135e6b8f306d1f54278968c576f3ceccc4e7
An upcoming change to Go 1.7 allows the json package to be able to encode maps
with the integer keys. Thus, this is no longer a good way to generate intentional
JSON failures.
Reference:
f05c3aa24d
Dmitri Shuralyov
Glenn Lewis
Huy Tr
Will Norris
Carlos Alexandro Becker
Hanno Hecker
Gabe Rosenhouse
Yannick Utard
Matthew Dempsky
Billy Lynch
Beshr Kayali
kujenga
Ainsley Chong
Garrett Squire
Bryan Boreham
Joe Tsai
Carl Jackson