> What's the benefit of returning true rather than the object?

Not a huge one... I don't mean to argue really, just voicing an opinion. To me (and I think a Ruby convention) `?` is literally asking a question, in this context "does this thing exist" :

```
me: "Does foo exist?" 
client: "foo"
me: "I guess so"
```
You're right though, in the context of an API client it's nice that after checking existence I already have `foo` and don't have to ask for it once I know it exists. 

> boolean_from_response is used for api calls that return 204, aka No Content

I jumped the gun there using `boolean_from_response` as an example :) 

> every call counts

Very true, and this reason probably trumps my objection. 

> I'm beginning to wonder if this should be the default behavior for all GET calls. Asking consumers to handle Octokit::NotFound seems heavy handed. Then we could have the ? variations check for truthiness. It would be a big change but might make the developer experience more pleasant. Thoughts?

Meaning all `?` methods like this (if something exists, etc) would return the Hashie and not boolean? For an API wrapper like this, I could buy in. If we think that's a route to a better and consistent experience, then great.