Closes #437.
Closes #446.

Change-Id: I7a9bd0717310ef016b2695fe0e5cffb8e8b86ff8

Change-Id: I8d2c9474de1585936f5cd7093b1a7404de6ac76d

Fixes #460.
Closes #463.

Change-Id: I34688c42a9328af10b4b61546e8bfd2c95c893aa

Change-Id: I86b10e5038a8292337486d40fd9d0d8310e2c0c3

Fixes #464.
Closes #465.

Change-Id: I9bde509ef6bf9382c48344e58d4a77da4b33e4a3

Closes #415.
Closes #447.

Change-Id: I36d64eb59d494afcc872a04a1da9e0b11f396e46

Fixes #458

Change-Id: Iba31c9762d66cf42198009fcf7ae074211679d1a

Generalise and add to PullRequestsService URL test

Fixes #453.
Closes #454.

Change-Id: Iaee7d8498d1d6a0813bbba14261e4393f77c9d1f

Closes #443.

Change-Id: I7c30d4091b11216e0aa1189abe001ac2e7476e49

Full documentation of StatusEvent webhook here:
https://developer.github.com/v3/activity/events/types/#statusevent

Use RepositoryCommit type for Commit field in StatusEvent.

Fixes #448.
Closes #449.

Change-Id: I9a2936a1893f50c3b507f6f295428db85ecf932b

Closes #436.

Change-Id: I02f7503a362ffc5ec09e24d0e3da0f8adfcd4b0c

The author JSON is in the format of a user, not a commit author, and so
the author field on all the release fetching methods were nil.

Closes #439.

Change-Id: Ifc1e79a3c92b27ea65618b16a3a2fd2eb2873710

It's similar to RateLimitError, but it's a different type of rate limit
error. It is documented at:

https://developer.github.com/v3/#abuse-rate-limits

Parse and include the Retry-After header value, if present. It is
documented at:

https://developer.github.com/guides/best-practices-for-integrators/#dealing-with-abuse-rate-limits

According to GitHub support, its type is an integer value representing
seconds.

Helps #431.

Fixes #432.

Change-Id: I4792114482f412f0eff54a6899a759fc9393ff88

Change-Id: Ia98b6c6aaaa579642fc097ac48ab7cb064eaf281

Add support for the new webhooks event for installations.
See: https://developer.github.com/early-access/integrations/webhooks/

Closes #434.

Change-Id: I74d3d50cb6b350322fc4515ad70097f0f70ae478

Closes #427.

Change-Id: I67faac8df63e0d55fcce4ca5f9ab50e26c04d6b3

Change-Id: Ia2ea767cc4da4a66ad20fab0382def0c10a688b3

Signed-off-by: Dave Henderson <dhenderson@gmail.com>

GitHub search API ratelimits are changed recently.
Reference: https://developer.github.com/v3/search/#rate-limit

Rate limit for unauthenticated requests change from 5 to 10 per minute.
And, rate limit for authenticated requests change from 20 to 30 per minute.

Signed-off-by: Yumikiyo Osanai <yumios.art@gmail.com>

Closes #424

Fixes #420
Closes #423

Fixes #417
Closes #418

Added the field incomplete_results. It is docummented on https://developer.github.com/v3/search/#timeouts-and-incomplete-results

Refs #103
Closes #411.

Change-Id: Ia61f48de052fd61a98357ba6182ead613b454fa3

Change-Id: I9a984b191e75fcd9e9fc3ca4ac563100464b9845

Refs #408

Closes #408

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

Change-Id: I17b9482ac3c49af59b6d0b662a6e7d720073651d

Fixes #394.
Closes #405.

Change-Id: I00240a792bfcafd744e57a130af3168482f235d9

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/#parameters

Fixes #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.

Fixes #399.
Fixes #401.

Change-Id: I97be757ad8672c649076ecbb0a51d60576d29164

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.

This change makes the code more consistent with the rateMu below.

This is a followup to https://github.com/google/go-github/pull/390#discussion_r68863652.

Closes #396.

Change-Id: I0fc8b280911f9171fb4d8e3fa60cf6d53b64a65b

Fixes #397.

Change-Id: I30ce336e3a36cf5758b9bf52b9dd77f7c1df5f27

Change-Id: I9668e8806934438062bac3f34e4759d44b5f63f4

In
[events](https://developer.github.com/v3/activity/events/types/#pullrequestevent),
the `id` field is present both in the Issue and PullRequest objects.

This PR adds them.

Change-Id: Ib5fd4e99b88ff01e3363e049177326b7ee97be93

Closes #342.

Change-Id: I8ba9587109cecf9ba5cb64efa20e58ecb1c7bfe0

Closes #391.

Change-Id: Ie5bca9e80c5d1a1348f640a1a75063bac63f539a

Fixes #389
Fixes #390

GitHub API docs: https://developer.github.com/v3/oauth_authorizations

Fixes #348.
Closes #388.

Change-Id: I795b1c0e10bde10a1bc9aaa4594af4c91e07962d