Fixes #311.

Change-Id: I334b9e22e748d96a62b0c7f59690c1a998a3c802

Fixes #308.
Fixes #309.

Change-Id: I71d1422c90f32cc6e6834ed428a311a2b2b88778

Change-Id: Ic6c776632587436d8b2a7810521f1a5ca1eae815

Additional fields (html_url, labels_url, id, closed_at) pulled from
https://developer.github.com/v3/issues/milestones/

Fixes #295

Fixes #297
Fixes #298

Change-Id: Ib17c43b368a0d0ee1a33690c17ad7c0f4dab55e5

Fixes #228
Fixes #301

Change-Id: I43d414332baa87b430487ea03d125633f8e40bd5

Change-Id: I385c22c290dd550c37ee7b3632a1a690cfaa36d7

Change-Id: I68a0d4fc72a4bd298298759ac70c0a2e8d83c00a

In V3 of the GitHub API, pull request comments are created in two ways. The
first way is to create a comment on a specific line of a file in a commit
with the following parameters:

| Name      | Type    | Description                                            |
|-----------|---------|--------------------------------------------------------|
| body      | string  | Required. The text of the comment                      |
| commit_id | string  | Required. The SHA of the commit to comment on.         |
| path      | string  | Required. The relative path of the file to comment on. |
| position  | integer | Required. The line index in the diff to comment on.    |

And the second way is through a reply to an existing comment with the following
parameters:

| Name        | Type    | Description                           |
|-------------|---------|---------------------------------------|
| body        | string  | Required. The text of the comment     |
| in_reply_to | integer | Required. The comment id to reply to. |

This commit adds support for the second (or "Alternative Input" according to
the GitHub docs) way.

Change-Id: Ia4888efa18c557a31af7093cfa449a67650afa20

Change-Id: I013dcbfb58ec10756c7b4e4bae6fe79b5e7c0062
Fixes #287

- simplify CLA text slightly
- clarify naming convention for .go files
- add "Maintainer's Guide" to document how I handle merging in
  contributions

fixes #283

Fixes #279.

Change-Id: I55ffdadfe5970d664ac94048e8bc2b8f5d935903

Fixes #152.

Add tests for RateLimitError.

Refactor populateRate into a more general parseRate.

Rate is now a method, not a field.

Mention RateLimits rather than RateLimit since the latter is deprecated.

Use Go convention for marking deprecated identifiers. See
257114af91.

fixes: #131,#271

fixes #274

fixes #272

Fixes #263.

Closes #265.

As with the previous key added in 19c0916, I deleted the associated
private key using /usr/bin/shred.  But of course, I have no way to prove
that.  Again, all the more reason to always use a test account when
running these integration tests.

see 92bbb1ce51

This adds support and integration tests for editing branch protection.

For more information about the preview see here:
https://developer.github.com/changes/2015-11-11-protected-branches-api/

This adds only retrieving the information and not setting it. Setting
will come in a later commit (if that one here is okay).

I tried to follow the naming guidelines as much as possible and
hopefully I made it right the first time. :-)

Adding the new BasicAuthTransport raises the minimum required version of
go to 1.4.

Add a new error type, TwoFactorAuthError, which identifies the need to
include a one-time password when using Basic Auth for a user with
two-factor auth enabled.

An example of using both the new transport and error type can be seen in
examples/basicauth/main.go.

fixes #258

Both:
https://developer.github.com/v3/issues/#list-issues
https://developer.github.com/v3/issues/#list-issues-for-a-repository

State that the default is `desc` for direction. (As does my results). So
update the comment.

In particular, this handles the case of trying to decode No Content
(204) responses.