You were right, this throws a different exception to the one we want.

We've been using `ctor` checks (like [this one](https://github.com/octokit/octokit.net/blob/master/Octokit/Clients/AssigneesClient.cs#L19)) to catch most of the bad input like that. Would that be worth plugging into these classes?