Use tmm1/test-queue

15s down to 3s on my MBA
Merge pull request #239 from ctshryock/test-queue

Use tmm1/test-queue
Loosen required_rubygems_version for compatibility with Ubuntu 10.04
Add .test_queue_stats to .gitignore
Merge branch 'master' of https://github.com/pengwynn/octokit
Implement C-U-D for Contents API
Add Octokit::Stats for GitHub stats apis
Merge pull request #243 from pengwynn/stats

Add Octokit::Stats for GitHub stats apis
File object support or Contents API C-U-D
Merge pull request #241 from pengwynn/contents-crud

New Contents API methods
Ensure file content is properly Base64 encoded

When making a call to the `create_contents` method, the Base64-encoding is causing
Octokit to throw an `UnprocessableEntity` exception, complaining that the content
is not valid Base64.

See the error below:

```ruby
Octokit::UnprocessableEntity: PUT https://api.github.com/repos/Sage/sageone_help_uk/contents/_help/bbb.textile: 422: content is not valid Base64
from /usr/local/opt/rbenv/versions/1.9.3-p327/lib/ruby/gems/1.9.1/bundler/gems/octokit-50c53ea2579f/lib/faraday/response/raise_octokit_error.rb:22:in `on_complete'
```

It's because of this issue documented here:

http://stackoverflow.com/questions/2620975/strange-n-in-base64-encoded-string-in-ruby

Where the call to Base64 encoding is happening, I've added a small piece of logic
to mimic Ruby 1.9s `strict_encode64` functionality, ensuring we're backward compatible
to Ruby 1.8.7.
Merge pull request #245 from damian/base64_encoding_issue

Ensure file content is properly Base64 encoded
Update README with new repo home
Update octokit.gemspec with new homepage
Merge pull request #246 from czarneckid/patch-1

Update octokit.gemspec with new homepage
Fixed docblock return in users remove_email()
Merge pull request #253 from dmyers/docs

Fixed docblock return in users remove_email()
Make sure `all_repositories` respects the api endpoint.
Merge pull request #254 from octokit/enterprise-fix-repositories

Fix all_repository requests for Enterprise