Fix the docs.
Add new testimonial
Fix a few doc build errors.
Closes #95

Unpin the version of requests we're requiring.
Future proofing against requests

Oh yeah, the GitHub object can now be used as a context manager! Woohoo! Stole
the inspiration from requests.Session.
Fix setup.py failure on Windows.
Fix the documentation for GitHub.iter_repos
Add link to license.

This just never got added in for whatever reason.
Update Repository.master_branch for API changes.

While working on a project using github3.py, I noticed `repo.master_branch` was
always returning `''`, even after doing a `repo.refresh()`.  This didn't seem
right, so I went digging with pdb and found the attribute to be named
`default_branch` instead.

The GitHub API docs[0] use `master_branch` in all their example responses, but
also mention `default_branch`.  I think they changed the name and forgot to
update the documentation.

Since the tests for this project use a static JSON response, there were no test
failures.  I updated the file to what I have experienced, but you should
double-check me on that.

[0]: http://developer.github.com/v3/repos/
Add myself to AUTHORS.
Fix test for unstarring gist.
Fix unstarring gist.
Update the repo fixture.

Add master_branch attribute to Repository
Merge branch 'pr/102' into develop

Conflicts:
	AUTHORS.rst

Put them in chronological order (sort of)
There's no need to test the attribute
Fixes #106

We were trying to send the list of Label objects to requests and json.dumps
was throwing a TypeError since the repr of a Label is <Label [labelname]>
instead of labelname. So we need to "normalize" the labels before sending them
to the JSON serializer.

Thanks to @alejandrogomez for the bug report. This is a huge issue.
Update Repository.master_branch for API changes.

While working on a project using github3.py, I noticed `repo.master_branch` was
always returning `''`, even after doing a `repo.refresh()`.  This didn't seem
right, so I went digging with pdb and found the attribute to be named
`default_branch` instead.

The GitHub API docs[0] use `master_branch` in all their example responses, but
also mention `default_branch`.  I think they changed the name and forgot to
update the documentation.

Since the tests for this project use a static JSON response, there were no test
failures.  I updated the file to what I have experienced, but you should
double-check me on that.

[0]: http://developer.github.com/v3/repos/
Add myself to AUTHORS.
There's no need to test the attribute
Start getting caught up