Fixes references to depreciated goauth2 libaray and replaces example
with the recomended oauth2 implimentation.

This integer exposes the number of comments that have been posted for that commit on GitHub.

It is documented at https://developer.github.com/v3/repos/commits/.

https://developer.github.com/v3/repos/releases/#create-a-release

Fixes #159

this method actually returns RepositoryCommits (go-github's term for
this, not GitHub's) rather than Commits.  They are very, very close in
structure (which is likely why this has gone unnoticed for so long), one
of the primary differences being that RepositoryCommits exposes the
GitHub identity of the commit author and committer if possible.

Add ListOptions to PullRequestListCommentsOptions and
IssueListCommentsOptions

fixes #143

These changes are strictly violations of any style guide (I don't
think?), but are just to make tests in go-github more consistent,
particularly in use of 'got' and 'want' vars.  In doing this, I found
several places where those two got reversed in the error message (hint:
'got' always comes first in go)

okay, so these aren't really that useful buy hey, why not? :)

               MMM.           .MMM
               MMMMMMMMMMMMMMMMMMM
               MMMMMMMMMMMMMMMMMMM      __________
              MMMMMMMMMMMMMMMMMMMMM    |          |
             MMMMMMMMMMMMMMMMMMMMMMM   | Ship It! |
            MMMMMMMMMMMMMMMMMMMMMMMM   |_   ______|
            MMMM::- -:::::::- -::MMMM    |/
             MM~:~   ~:::::~   ~:~MM
        .. MMMMM::. .::::. .::MMMMM ..
              .MM::::: ._. :::::MM.
                 MMMM;:::::;MMMM
          -MM        MMMMMMM
          ^  M+     MMMMMMMMM
              MMMMMMM MM MM MM
                   MM MM MM MM
                   MM MM MM MM
                .~~MM~MM~MM~MM~~.
             ~~~~MM:~MM~~~MM~:MM~~~~
            ~~~~~~==~==~~~==~==~~~~~~
             ~~~~~~==~==~==~==~~~~~~
                 :~==~==~==~==~~

A recent update to the GitHub API changed some undocumented behavior. Previously
a nonexistent base_tree and an empty string base_tree were treated the same, but
now the empty string case will fail with "422 base_tree is not a valid oid".

The release assets are included in the release object, but they are not being
parsed currently. To get the list of release assets, one must use
ListReleaseAssets, which is one extra unnecessary HTTP request.

This commit adds Assets field to RepositoryRelease struct so that the release
assets are immediately available right after calling ListReleases.

Signed-off-by: Ondřej Kupka <ondra.cap@gmail.com>

The git ref methods were mostly written to not expect the 'refs/' prefix
on ref names, even though it is included the ref.Ref value returned by
GitHub.  This resulted in ref values returned from some methods that
couldn't be passed to other methods.  In reality, ref names passed to
these methods should normally include the prefix, but this change
supports either form for backwards compatibility.

Fixes #133

Latest blog post:
https://developer.github.com/changes/2014-08-28-accepting-organization-invitations-from-the-api/

- TeamMembership has been renamed to Membership, since it now covers
  organization membership as well
- Status field renamed to State
- added new methods: ListOrgMemberships, GetOrgMembership,
  EditOrgMembership

Adds PullRequestEvent, IssueCommentEvent, and IssueActivityEvent

ref: #130

- BrowserDownloadUrl
- Uploader

See
https://developer.github.com/v3/repos/releases/#upload-a-release-asset

This is required for non-owners to create organization repos on github.